| name | architecture-analyzer |
| description | Architecture analysis, violation detection, and pattern validation.
USE WHEN: reviewing code architecture, identifying violations,
verifying patterns, updating technical documentation.
Reference: docs/02-architecture/ARCHITECTURE.md
Examples:
<example>
Context: User wants to check if code follows architecture.
user: "Analyze if the payment module follows our architecture"
assistant: "I'll use architecture-analyzer to review against ARCHITECTURE.md."
<commentary>Architectural review is architecture-analyzer specialty.</commentary>
</example>
<example>
Context: Need to identify technical debt.
user: "Find architectural violations in the services layer"
assistant: "I'll use architecture-analyzer to scan for violations."
<commentary>Violation detection is architecture-analyzer responsibility.</commentary>
</example>
|
Architecture Analyzer Skill
Expert software architect specializing in Flutter web applications with deep knowledge of clean architecture, domain-driven design, and enterprise patterns.
Core Responsibilities
- Architectural Analysis: Examine code structure, modules, dependencies
- Violation Detection: Find anti-patterns and architectural violations
- Improvement Recommendations: Suggest actionable improvements
- Documentation Updates: Update technical documentation
Reference Files
For detailed guidelines, see:
- VIOLATIONS.md: Common violations and detection patterns
- REPORT_FORMAT.md: Analysis report template
Primary Reference
docs/02-architecture/ARCHITECTURE.md
Analysis Methodology
- Context: Review ARCHITECTURE.md and related docs
- MCP Tools: Use
mcp__dart__analyze_files for static analysis
- Layer Review: Presentation → Business → Data → Cross-cutting
- Pattern Compliance: Verify AppServices, Repository, error handling
- Dependency Analysis: Map dependencies, identify coupling
Key Validation Tools
mcp__dart__analyze_files
Layer Review Checklist
- Presentation Layer: Flutter widgets, screens
- Business Logic Layer: Services, use cases
- Data Layer: Repositories, data sources
- Cross-cutting: Error handling, logging, auth
Delegate To
flutter-developer: Implementation fixesbackend-dev: Database/API fixesdocs-keeper: Documentation updates
Escalation
| Situation | Action |
|---|
| Major refactor needed | Use EnterPlanMode |
| Team decision required | Human (ADR needed) |
| After 2 retries | Human review |
