Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From code-architect
Generates a structured architecture document from user requirements, covering system boundaries, components, data flow, technology choices, and risks.
How this command is triggered — by the user, by Claude, or both
Slash command
/code-architect:architectThe summary Claude sees in its command listing — used to decide when to auto-load this command
Generate a comprehensive architecture document for a system or feature based on requirements. ## Steps 1. Gather requirements from the user: What is being built? What are the constraints? 2. Define the system boundaries: 3. Design the high-level architecture: 4. Detail each component: 5. Address cross-cutting concerns: 6. Document technology choices with rationale. 7. Identify risks and mitigation strategies. ## Format ## Rules - Always start with requirements before designing solutions. - Prefer simple architectures over complex ones. - Every technology choice must have a stated ...
Generate a comprehensive architecture document for a system or feature based on requirements.
# Architecture: <System Name>
## Overview: <one paragraph summary>
## Components: <list with responsibilities>
## Data Flow: <sequence of interactions>
6plugins reuse this command
First indexed Mar 30, 2026
npx claudepluginhub avelikiy/awesome-claude-code-toolkit --plugin code-architect/architectGenerates a structured architecture document from user requirements, covering system boundaries, components, data flow, technology choices, and risks.
/create-architecture-documentationAnalyzes system architecture and generates comprehensive documentation across context, containers, components, data, security, and quality. Supports C4, Arc42, ADRs, and diagram-as-code via PlantUML or Mermaid.
/architectGuides system design and architecture planning with structured output including trade-off analysis, ADRs, and ASCII diagrams before implementation.
/designDesigns system architecture with phased roadmap and technology recommendations for a given system or feature description. Produces a comprehensive document covering components, trade-offs, risks, and deployment.
/askProvides architectural consultation and strategic guidance for technical questions, synthesizing insights from systems design, technology strategy, scalability, and risk analysis.