architecture-analyzer

weppa-cloud's avatarfrom weppa-cloud

Architecture analysis, violation detection, and pattern validation.USE WHEN: reviewing code architecture, identifying violations,verifying patterns, updating technical documentation.Reference: docs/02-architecture/ARCHITECTURE.mdExamples:<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>

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 31, 2025
[Architecture Design]

When & Why to Use This Skill

The Architecture Analyzer is a specialized Claude skill designed for software architects and developers to maintain structural integrity in complex codebases, particularly Flutter web applications. It performs automated architectural reviews, detects pattern violations, and ensures compliance with Clean Architecture and Domain-Driven Design (DDD) principles. By analyzing dependencies and layer boundaries, it helps teams identify technical debt and keep technical documentation synchronized with the actual implementation.

Use Cases

  • Architectural Compliance Review: Automatically analyze new modules or feature branches to ensure they strictly follow the project's defined ARCHITECTURE.md guidelines and layer constraints.
  • Technical Debt & Violation Detection: Scan specific layers (Presentation, Business, Data) to identify anti-patterns, tight coupling, or architectural violations that compromise maintainability.
  • Design Pattern Validation: Verify the consistent implementation of enterprise patterns such as Repositories, AppServices, and standardized error handling across the entire application.
  • Documentation Maintenance: Review code structure changes to provide actionable recommendations for updating technical documentation, ensuring that architectural diagrams and docs reflect the current state of the code.
namearchitecture-analyzer
description|
USE WHENreviewing code architecture, identifying violations,
Referencedocs/02-architecture/ARCHITECTURE.md
ContextNeed to identify technical debt.
user"Find architectural violations in the services layer"
assistant"I'll use architecture-analyzer to scan for violations."

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

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