architecture
Define system design, interfaces, and data flow consistent with the approved plan and policies.
When & Why to Use This Skill
This Claude skill streamlines the software development lifecycle by defining robust system designs, interfaces, and data flows. It helps architects and developers transform high-level plans into structured outlines, ensuring alignment with organizational policies and technical constraints while avoiding premature implementation details.
Use Cases
- Drafting high-level system designs for new software projects to align stakeholders on technical direction and component responsibilities.
- Defining clear API interfaces and data integration patterns between microservices to ensure seamless communication.
- Documenting architectural decisions, trade-offs, and data flow diagrams to ensure compliance with security and operational policies during the planning phase.
| name | architecture |
|---|---|
| description | Define system design, interfaces, and data flow consistent with the approved plan and policies. |
Purpose
Create an architecture outline with components, responsibilities, interfaces, data flows, and decision notes ready for review.
Inputs
- Approved plan and goals
- Constraints and applicable policies
- Existing system context and boundaries
Steps
- Confirm scope, constraints, and non-functional requirements.
- Identify components, responsibilities, and interfaces.
- Describe data flow, integrations, and edge cases.
- Capture decisions, trade-offs, and open questions for review.
Outputs
- Architecture outline with components, interfaces, data flows, and decision notes.
Failure modes
- Introducing new scope or features
- Omitting constraints, edge cases, or policy alignment
- Providing implementation details instead of architectural guidance