# Architecture Analyzer

> 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>

- Skill: `majiayu000/architecture-analyzer` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/architecture-analyzer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/architecture-analyzer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/architecture-analyzer

---


# 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

1. **Architectural Analysis**: Examine code structure, modules, dependencies
2. **Violation Detection**: Find anti-patterns and architectural violations
3. **Improvement Recommendations**: Suggest actionable improvements
4. **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

1. **Context**: Review ARCHITECTURE.md and related docs
2. **MCP Tools**: Use `mcp__dart__analyze_files` for static analysis
3. **Layer Review**: Presentation → Business → Data → Cross-cutting
4. **Pattern Compliance**: Verify AppServices, Repository, error handling
5. **Dependency Analysis**: Map dependencies, identify coupling

## Key Validation Tools

```bash
mcp__dart__analyze_files  # Static analysis
```

## 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 fixes
- `backend-dev`: Database/API fixes
- `docs-keeper`: Documentation updates

## Escalation

| Situation | Action |
|-----------|--------|
| Major refactor needed | Use EnterPlanMode |
| Team decision required | Human (ADR needed) |
| After 2 retries | Human review |