# Project context fields — what each `adia-info` field drives

Load this when the live probe (SKILL.md's `## Current project context` block)
returns a field whose consequence isn't obvious from the name alone.

| Field | Drives |
| --- | --- |
| `isFrameworkMonorepo` | `true` → STOP: this is framework authoring, not consumer work — route to the adia-ui-forge plugin |
| `renderingMode` · `framework` | which `host-wiring` path applies; the markup composed here is identical either way |
| `adiaPackages` vs `installedVersion` | declared range vs actually-installed — a mismatch or `null` install means `npm install` before debugging any "component renders wrong" |
| `shellsUsed` | compose inside the existing shell's regions; never scaffold a second shell beside one |
| `registrationFiles` | where imports wire up — a composite's missing internal-primitive import lands in one of these files |
| `theme` | which knobs are already on (`themesCss` / `dataScheme` / `namedTheme`); scheme and register edits go where these already live |
| `a2uiMcp` | `configured: false` → MCP-assisted composition is unavailable; hand-compose, and validate when the server is wired |