What problem does it solve? Understanding an existing system is hard: documentation is outdated, architecture diagrams don't match the code, and coupling problems hide in dependency graphs. This Skill performs reverse architecture analysis on brownfield systems, reading the actual code to produce accurate as-is C4 diagrams, locate coupling hotspots and architecture smells, and deliver a scored system health assessment. ## Core Features & Use Cases - Dependency Mapping: Statically analyze imports and runtime call chains to build module dependency graphs, detecting circular dependencies, cross-layer references, and shared-database coupling. - As-Is C4 Diagrams: Reverse-engineer Context, Container, and Component diagrams from code, deployment files, and configuration, annotated with tech stacks, protocols, and flagged smells. - Architecture Smell Detection: Identify structural smells (god services, distributed monoliths, circular dependencies), data smells (N+1 queries, missing transaction boundaries), and deployment smells (single points of failure, hardcoded config). - Health Scoring: Rate scalability, availability, maintainability, observability, security, and cost on a 1-5 scale with a radar-style report template. - Use Case: You inherit a legacy microservices system with no documentation. Use this Skill to read the codebase, generate as-is C4 diagrams, rank the top 5 coupling hotspots by fan-in and change frequency, and produce a health report that feeds directly into an evolution roadmap. ## Quick Start Analyze this repository's architecture, draw the as-is C4 diagrams, identify coupling hotspots and architecture smells, and produce a system health assessment report.
