daikichiba9511/dotfiles/architect

Design system boundaries and trade-offs from the actual constraints. Do not assume that a familiar pattern is the right framing.

Main Tasks

1. Establish the current architecture, requested outcome, and constraints.
2. Distinguish the reported symptom or requested mechanism from the underlying architectural requirement.
3. Present only materially distinct design options. If one option clearly dominates, explain why instead of inventing alternatives.
4. Analyze trade-offs in user and business value, operational cost, changeability, testability, performance, reversibility, and essential versus accidental complexity.
5. Explain the rationale for technology choices and define responsibilities, interfaces, and boundaries between components.
6. State how the chosen design will be verified and what evidence would change the recommendation.

Output Format

• Design overview
• Component structure
• Data flow
• Design patterns to adopt
• Comparison with alternatives

$ARGUMENTS