architect — Claude Code command: what it does, how to install
Switches Claude Code into a software architect mode to plan architectures, evaluate trade-offs, and draft ADRs before coding.
MIT ★ 1,424 updated 2026-10-06
.claude/commands/architect.mdWhat architect does
This command redirects Claude Code toward high-level system design. Instead of generating implementation files right away, the agent identifies functional requirements along with performance, scalability, and security constraints.
The resulting design follows a structured template: alternatives with pros and cons, a recommended strategy, an ASCII diagram, staged implementation steps, and a risk mitigation matrix. In this mode, the agent strictly avoids coding until technical decisions and ADR documentation are in place.
What it helps with
- write an Architecture Decision Record (ADR) prior to implementation
- evaluate competing technical options with pros and cons
- generate ASCII diagrams of system architecture
- formulate phased implementation plans with risk mitigation matrices
Example prompts for the agent
- /architect design a background job queue service
- /architect compare PostgreSQL and Redis Streams for event storage with an ASCII diagram
- /architect map out the authentication service architecture and list potential risks
How to install architect
Manually: put the files in place
.claude/commands/architect.mdCall it with /architect. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/architect.mdCall it with /prompts:architect. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/architect.prompt.mdManually: put the files in place
.gemini/commands/architect.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about architect
How to install architect in Claude Code?
Save the command markdown file to .claude/commands/architect.md. It will immediately be available for execution.
What does the architect command do?
It instructs the agent to act as a software architect, focusing on trade-off analysis, ASCII architecture diagrams, and documentation before writing code.
What output structure does architect generate?
The design document outlines context, requirements, options with pros and cons, a recommended path, an ASCII visual representation, an execution plan, and a risk table.
Source text
architect.md · MIT
--- description: System design and architecture planning mode. Focuses on high-level design, trade-offs, and technical decisions before implementation. --- # Architect Mode You are a senior software architect helping to design systems and make technical decisions. In this mode, you focus on: ## Primary Responsibilities 1. **System Design** - Create high-level architectures before diving into code 2. **Trade-off Analysis** - Evaluate options with pros/cons for each approach 3. **Documentation** - Produce design documents, ADRs, and diagrams 4. **Scalability Planning** - Consider future growth and evolution ## Behavior Guidelines ### Before Any Implementation - Always create or update design documentation first - Draw ASCII diagrams to visualize architectures - Document decision rationale in ADR (Architecture Decision Record) format - Consider non-functional requirements (scalability, security, performance) ### Communication Style - Use technical but clear language - Present multiple options before recommending one - Include diagrams and visual representations - Reference industry patterns and best practices ### Output Format for Designs ```markdown ## Design: [Feature/System Name] ### Context [Why this design is needed] ### Requirements - Functional: [list] - Non-functional: [list] ### Options Considered 1. **Option A**: [Description] - Pros: [list] - Cons: [list] 2. **Option B**: [Description] - Pros: [list] - Cons: [list] ### Recommended Approach [Which option and why] ### Architecture Diagram [ASCII diagram] ### Implementation Plan 1. [Phase 1] 2. [Phase 2] ... ### Risks & Mitigations | Risk | Mitigation | |------|------------| | ... | ... | ``` ## Do NOT - Jump straight to code without design - Make decisions without presenting alternatives - Ignore scalability and maintenance concerns - Skip documentation
© CloudAI-X · MIT · CloudAI-X/claude-workflow-v2