| name | setup-architect |
| description | Sets up and installs the AI Software Architect framework in a NEW project for the FIRST time. Use when the user requests "Setup .architecture", "Setup ai-software-architect", "Initialize architecture framework", "Install software architect", or similar setup/installation phrases. Do NOT use for checking status (use architecture-status), creating documents (use create-adr or reviews), or when framework is already set up. |
Setup AI Software Architect Framework
Sets up and customizes the AI Software Architect framework for a project.
Process
1. Verify Prerequisites
- Check
.architecture/.architecture/exists (cloned framework) - Confirm we're in project root
2. Analyze Project
Identify:
- Primary languages (JavaScript/TypeScript, Python, Ruby, Java, Go, Rust)
- Frameworks (React, Vue, Django, Rails, Spring, etc.)
- Testing setup, CI/CD, package managers
- Project structure and patterns
3. Install Framework
cp -r .architecture/.architecture/* .architecture/
rm -rf .architecture/.architecture
mkdir -p .coding-assistants/{claude,cursor,codex}
mkdir -p .architecture/decisions/adrs
mkdir -p .architecture/{reviews,recalibration,comparisons}
cp .architecture/templates/config.yml .architecture/config.yml
4. Customize Members
Update .architecture/members.yml with specialists for detected tech stack:
- JavaScript/TypeScript: JavaScript Expert, React/Vue/Angular Specialist, Node.js Expert
- Python: Python Expert, Django/Flask/FastAPI Specialist
- Ruby: Ruby Expert, Rails Architect
- Java: Java Expert, Spring Boot Specialist
- Go: Go Expert, Microservices Architect
- Rust: Rust Expert, Systems Programmer
Use this format:
- id: javascript_expert
name: "Alex Rivera"
title: "JavaScript Expert"
specialties: ["Modern JavaScript/TypeScript", "Frontend architecture", "Build tools"]
disciplines: ["Clean code", "Performance", "Cross-browser compatibility"]
skillsets: ["ES6+", "Async programming", "Module systems"]
domains: ["Web applications", "Node.js backends", "Build pipelines"]
perspective: "Focuses on JavaScript best practices and modern features"
5. Customize Principles
Add framework-specific principles to .architecture/principles.md:
- React: Component composition, hooks, props down/events up
- Rails: Convention over configuration, DRY, fat models/skinny controllers
- Django: Explicit over implicit, reusable apps, use built-in features
6. Update CLAUDE.md
Append (don't include setup instructions, only usage):
## AI Software Architect Framework
### Commands
- Create ADR: "Create ADR for [decision]"
- Architecture Review: "Start architecture review for version X.Y.Z"
- Specialist Review: "Ask [role] to review [target]"
- List Members: "List architecture members"
- Status: "What's our architecture status?"
See `.architecture/` for all documentation.
7. Cleanup
Remove from .architecture/:
- Framework's README.md, USAGE*.md, INSTALL.md
.git/directory with CRITICAL SAFEGUARDS:- Verify we're in project root (check for project markers: package.json, .git in parent, etc.)
- Verify
.architecture/.git/exists before attempting removal - Verify
.architecture/.git/configcontains template repository URL (not project URL) - Use absolute path:
rm -rf $(pwd)/.architecture/.git - Never use wildcards with rm -rf
- STOP AND ASK USER if any verification fails
- Only remove from .architecture, NEVER project root .git!
8. Initial Analysis
Create .architecture/reviews/initial-system-analysis.md:
- Have each member from members.yml analyze the system from their perspective
- Include: system structure, patterns, strengths, concerns, recommendations
- Add collaborative discussion synthesizing findings
- Prioritize recommendations (Critical/Important/Nice-to-have)
9. Report to User
Summarize:
- Customizations made (which specialists added, why)
- Key findings from initial analysis (top 2-3)
- Configuration: pragmatic mode (enabled/disabled), intensity level
- How to use framework with their stack
- Suggested next steps based on analysis
Error Handling
- No
.architecture/: Ask user to clone framework first - Already set up: Inform user
- Unclear project: Ask about architecture
Related Skills
After Setup:
- "List architecture members" - View the customized team
- "What's our architecture status?" - Verify setup completed correctly
- "Create ADR for [first decision]" - Start documenting
Initial Architecture Work:
- Review initial-system-analysis.md in .architecture/reviews/
- "Ask [specialist] to review [specific area]" - Deep-dive on analysis findings
- "Create ADR for [key decisions]" - Document important existing decisions
Workflow Examples:
- Setup → Review initial analysis → Create ADRs for key decisions → Status check
- Setup → List members → Ask specialists about specific concerns → Document findings
Notes
- Customize based on actual project, not every possible option
- Keep initial analysis thorough but focused
- Be specific about why each customization was made