Architecture Documentation

Architecture documentation can be automatically generated by analyzing your codebase to extract tech stack, components, data flow, and API patterns. The Skill produces a comprehensive architecture.md file with Mermaid diagrams and architectural decision records, eliminating manual discovery work and accelerating team onboarding.

Yes, architecture documentation supports both existing systems and new projects. For new systems, you describe your requirements and the Skill recommends appropriate tech stacks, architectural patterns, and deployment strategies, helping you define architecture before implementation begins.

Architecture documentation generates Mermaid system and component-level diagrams embedded directly in Markdown, a detailed architecture.md file, and a JSON summary capturing key architectural decisions with rationale, data-flow mapping, and explicit component and dependency analysis.

The Skill automatically regenerates architecture documentation from your current codebase or design inputs, making it ideal when docs/architecture.md is missing, outdated, or needs refreshing as part of feature-delivery workflows or team transitions.

For new projects, you provide your system requirements and constraints. The Skill then recommends tech stacks, architectural patterns, and deployment strategies tailored to your needs, delivering a complete architecture design with diagrams and decision documentation.

Yes, architecture documentation analyzes existing codebases without requiring modifications. It extracts architectural information directly from your code structure, dependencies, and patterns to generate documentation and diagrams reflective of your current system design.