Menu
Use when reviewing architecture decisions. C4 model, dependency inversion, hexagonal boundaries.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | architecture-review |
| description | Use when reviewing architecture decisions. C4 model, dependency inversion, hexagonal boundaries. |
∀ plan reviews (standard, complex). ∀ PRs that touch module boundaries.
| Aspect | Status | Finding |
|---|---|---|
| Layer dependency | pass/fail | ... |
| Module boundaries | pass/fail | ... |
| Port coverage | pass/fail | ... |
| Cross-cutting concerns | pass/fail | ... |
Use when making git commits. Conventional commit format and rules.
Use when running security review on a diff/PR/file. Research-vs-Reporting discipline, three-tier confidence gate, attacker-controllable taxonomy.
Use when invoking plannotator for approval review of generated .tff-cc milestone artifacts (plan, verification, spec).
Use when starting design or discovery work. MUST use before any creative work.
Use when the user wants to report a bug, file an issue, or send feedback about tff-cc. Triggers on phrases like 'report issue', 'file a bug', 'tff-cc broke', 'something is wrong with tff-cc', 'open an issue', '/report-issue'.
Use when creating, refining, or composing skills. Evidence-driven pattern analysis.
