architecture-design
Design system architecture with components, data flow, and boundaries. Use for non-trivial features.
When & Why to Use This Skill
This Claude skill streamlines the software development lifecycle by providing a structured framework for designing robust system architectures. It helps developers and architects define component responsibilities, map complex data flows, and establish clear system boundaries, ensuring that non-trivial features are built for scalability, maintainability, and technical clarity.
Use Cases
- New Feature Planning: Designing the structural blueprint for complex software modules, including component interactions and external API integrations before writing code.
- System Refactoring: Analyzing and redefining the boundaries of existing legacy code to improve modularity and reduce technical debt.
- Technical Documentation: Automatically generating standardized architecture.md files and Mermaid diagrams to communicate design decisions and trade-offs to stakeholders.
- Integration Strategy: Defining how new features will interact with existing databases, services, and third-party APIs to ensure seamless data flow.
| name | architecture-design |
|---|---|
| description | Design system architecture with components, data flow, and boundaries. Use for non-trivial features. |
Architecture Design
Design the component structure and interactions for a feature or system.
Process
- Review spec.md requirements
- Identify components and their responsibilities
- Define data flow between components
- Establish boundaries (APIs, databases, external services)
- Document patterns and trade-offs
Output
Create architecture.md using the template in templates/architecture.md.
Tips
- Use Mermaid diagrams for visual clarity
- Keep components single-responsibility
- Consider existing patterns in the codebase
- Document why decisions were made, not just what
- Identify integration points with existing code