architecture
Installation
SKILL.md
Architecture
Design the technical architecture for a set of requirements: components, data flow, dependency graph, tech stack decisions, integration points, and risks.
When to Use
- A PRD exists and the technical approach needs to be designed
- Before task breakdown — architecture defines WHAT components exist; breakdown defines the ORDER to build them
- When architectural decisions need to be documented (data model, API design, component structure)
- When integration with existing systems requires explicit mapping
When NOT to use: The technical approach is already documented in an architecture.md, or the change is trivial (single file, no architectural decisions).
Input
prd.mdfrom the artifact folder (required)context-map.mdfrom the artifact folder (required — for tech stack and existing patterns)brainstorming.mdfrom the artifact folder (recommended — for chosen direction rationale)