---
name: mcp-sophia-yii-developer
description: Develop and debug Sophia Framework 2 applications based on Yii 1.1, including FRM/APP/CLI-client layering, controllerMap overrides, RenderSettings forms and grids, Gii custom scaffolding, Cruge/RBAC permissions, exports, DB scripts, PHP syntax linting, and post-fix validation. Use this whenever the user asks to inspect, modify, generate, debug, review, or validate PHP/Yii code in a Sophia application, even if they only mention Yii, Sophia, Musa, controllerMap, RenderSettings, FrmGridView, Cruge, Gii, export, or script DB.
---

# MCP Sophia Yii Developer

Skill specialistico per Sophia Framework 2 / Yii 1.1. Usa `linter-node` per gate PHP e sidecar solo quando servono. Non e' orchestratore generalista.

## Quick Routing

| Scenario | Reference |
| :--- | :--- |
| Layer, override, `controllerMap` | [references/architecture-layers.md](references/architecture-layers.md) |
| `.env`, config, ambienti | [references/configuration-environments.md](references/configuration-environments.md) |
| CRUD, form, filtri, griglie | [references/render-settings-forms-grids.md](references/render-settings-forms-grids.md) |
| Export Excel/PDF/CSV/HTML | [references/export-management.md](references/export-management.md) |
| Permessi, menu, Cruge/RBAC | [references/cruge-permissions-menu.md](references/cruge-permissions-menu.md) |
| Gii/scaffold custom | [references/gii-code-generation.md](references/gii-code-generation.md) |
| Script DB, registry, tracking | [references/db-scripts-and-migrations.md](references/db-scripts-and-migrations.md) |
| Post-fix o review | [references/post-fix-checklist.md](references/post-fix-checklist.md), [references/pr-review-checklist.md](references/pr-review-checklist.md) |
| Routing cross-skill | [references/routing-matrix.md](references/routing-matrix.md) |

Usa `mcp-technical-analyst` se servono ticket/docs/commit/DB/allegati o conflitti tra prove. Usa `mcp-master-orchestrator` per discovery + fix + DB/browser/report.

## Regole Permanenti

1. Classifica layer prima del fix: `FRM`, `APP`, `CLI/client`; `cli` spesso e' specializzazione cliente, non command Yii.
2. Non usare Yii stock come default: verifica pattern Sophia, `controllerMap`, `RenderSettings`, helper e Gii custom.
3. Usa `project_path` della Sophia app per `.env`, config e asset; non leggere dominio dal repo MCP/cwd.
4. Lint PHP in audit per ogni `.php` toccato quando disponibile; niente fix automatici senza richiesta esplicita.
5. Nuove action, menu e pulsanti passano da `GetAbilitazioni`, ruoli o feature flag; niente permessi dispersi nelle view.
6. Griglia ed export sono contratti distinti; non copiare ciecamente colonne griglia nell'export.
7. Preserva compatibilita' legacy e fallback salvo richiesta contraria.
8. Local-first: reference inclusi prima, `docs-node` solo per verifica o convenzioni vive.

## Workflow Base

1. Identifica `project_path`.
2. Classifica scenario: CRUD, form/griglia, export, permessi, config, script DB, debug UI/runtime o review.
3. Classifica layer target e carica il reference minimo.
4. Ispeziona codice vicino e pattern gia presenti.
5. Esegui `lint_code` PHP in audit sui file toccati.
6. Applica modifica minima nel layer corretto.
7. Valida con lint, smoke applicativo, DB, browser o docs secondo impatto.
8. Chiudi con rischi residui, test eseguiti e nota cache/riavvio se applicabile.

## Sidecar

- `mcp-docs-navigator`: convenzioni Sophia vive e scaffale `sophia-apps-documentation`.
- `mcp-database-expert`: schema, query, dati, script DB, export e tracking.
- `mcp-browser-automation`: form, griglie Ajax, menu, download export, console e network.
- `mcp-git-mantis-workflow`: ticket, commit, branch, allegati e tracciabilita'.
- `mcp-code-reviewer`: review boundary layer, permessi, rendering, query, export e test gap.
- `mcp-office-expert`: export Excel/PDF o specifiche Office.

Se cambi solo skill/documentazione, non serve riavvio server MCP. Se cambi codice server MCP, informa che serve riavvio.