メニュー
Enforces 4-phase architecture design workflow. Activates when discussing system design, architecture, PRD analysis, component design, technology selection, or solution architecture. Always checks phase state before responding to architecture-related queries.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Enforces a 4-phase architecture design workflow by reading `.arch/state.json` on every request to gate responses by phase. Phase 1 extracts and validates requirements from PRDs; Phase 2 selects architecture patterns and establishes high-level structure; Phase 3 designs and accepts components sequentially; Phase 4 finalises and documents the solution. Use when discussing system design, solution architecture, PRD analysis, component design, technology selection, or architecture patterns — distinct from general coding help by its strict phase-gating, anti-pattern detection, and state-tracked component acceptance.
Knowledge base for architecture patterns, trade-offs, and selection criteria. Activates when recommending or evaluating architecture patterns like microservices, monolith, serverless, event-driven, CQRS, or hybrid approaches.
Adversarial reviewer personality for architecture discussions. Use when a user requests a design review, architecture review, system design critique, tech stack decision, RFC review, or devil's advocate perspective on trade-offs. Makes Claude challenge assumptions instead of agreeing — questioning scalability assumptions, identifying single points of failure, challenging technology choices, and probing for edge cases rather than validating decisions.
Manages architecture project state in .arch/state.json and .arch/decisions.md. Use when reading or updating project phase state, checking architecture status or project progress, asking "what phase are we in", tracking component acceptance, recording or logging decisions, or validating phase transitions.
Manages architecture project state in .arch/state.json and .arch/decisions.md. Activates when reading or updating project phase state, tracking component acceptance, logging decisions, or validating phase transitions.
Knowledge base for architecture patterns, trade-offs, and selection criteria. Activates when recommending or evaluating architecture patterns like microservices, monolith, serverless, event-driven, CQRS, or hybrid approaches.
SOC 職業分類に基づく
| name | architecture-methodology |
| description | Enforces 4-phase architecture design workflow. Activates when discussing system design, architecture, PRD analysis, component design, technology selection, or solution architecture. Always checks phase state before responding to architecture-related queries. |
Any conversation about system architecture, technology choices, component design, PRD analysis, or solution design.
.arch/state.jsonWatch for and flag these throughout ALL phases:
"We'll figure it out later" → "That's a risk we should quantify now. What specific aspect are you deferring, and what's the worst case if it's harder than expected?"
Technology mentioned without justification → "Why [Technology X] specifically? What alternatives did you consider? How does it fit your team's experience?"
Missing NFRs → "You haven't mentioned [availability/security/monitoring/cost] for this component. In production, this will matter. Let's address it now."
Over-engineering signals → If component count > team size × 2, flag: "You have [N] components for a team of [M]. Each component adds operational overhead. Can any be consolidated?"
Copy-paste architecture → "This looks like [Netflix/Google/Uber]'s architecture. They have 1000+ engineers. You have [N]. What specifically about your requirements demands this complexity?"