Auto-generated from: .mex/ — Last scanned: 2026-05-14T20:15:35.056025+00:00
AI Knowledge Base (.mex)
The .mex/ directory is the AI-readable project knowledge scaffold. It's used by Claude Code, Cursor, Windsurf, and other AI tools to understand the project without re-discovering context each session.
How It Works
- ROUTER.md -- session bootstrap file. AI agents read this first, then follow the routing table to load relevant context.
- Behavioural Contract -- every AI task follows: CONTEXT -> BUILD -> VERIFY -> DEBUG -> GROW.
- Context files -- domain knowledge that can't be derived from code alone.
- Patterns -- reusable task checklists (created from past sessions).
Context Files
| File | Description |
|---|---|
architecture | How the major pieces of this project connect and flow. Load when working on system design, integrati |
brand-guidelines | Geris corporate brand guidelines for all AI-generated visual assets — presentations, documents, diag |
conventions | How code is written in this project — naming, structure, patterns, and style. Load when writing new |
data-dictionary | |
dbt | dbt project specifics — dual-dialect handling, source configuration, model structure, and common got |
decisions | Key architectural and technical decisions with reasoning. Load when making design choices or underst |
devops-ci | Azure DevOps CI/CD pipeline configuration, Key Vault integration, and agent quirks. Load when workin |
fabric-deployment | Fabric deployment specifics — TMDL semantic models, Power BI reports, environment config, and pipeli |
fabric-platform-gotchas | Microsoft Fabric platform-specific behaviors, error codes, and API quirks that differ from SQL Serve |
presentation-design | Guide for creating Geris PowerPoint presentations — styling, modular building blocks, copywriting, a |
report-styling | |
setup | Dev environment setup and commands. Load when setting up the project for the first time or when envi |
stack | Technology stack, library choices, and the reasoning behind them. Load when working with specific te |
Patterns
11 task-specific patterns available:
add-data-sourceadd-dbt-modelapply-dictionary-learningsdebug-pipelinemodify-tmdlpromote-to-uatprovision-new-envrename-columnrestyle-reportupdate-docsworktree-lifecycle
For Developers
You don't need to read .mex files directly -- this page summarizes what's there. If you're working with an AI tool, it will load the relevant context automatically via ROUTER.md.