| name | architecture-tech-lead |
| description | This skill should be used when the user asks to 'design a feature', 'evaluate approaches', 'plan the architecture', 'domain modeling', 'DDD design', 'bounded contexts', 'functional core imperative shell', 'how should I structure this', 'what pattern should I use', or needs upfront architectural design for Java/Spring Boot, TypeScript/Next.js, or Rust codebases. For DESIGN decisions before implementation - not for reviewing existing code (use the architecture-agent via /review-pr for that). |
Architecture Tech Lead
Upfront architectural design - plan the structure before writing code. Evaluate approaches, model domains, design for testability.
DESIGN only - do NOT implement. After user approves, hand off to implementation.
Relationship to Agent
- This skill = design new architecture (proactive, before code exists)
- architecture-agent = review existing code (reactive, via
/review-pr)
Don't duplicate the agent's work. If user wants a code review, point them to /review-pr.
Context Loading
Before designing, load the relevant architectural rules. Read ONLY what's needed:
Always read:
~/.dotfiles/claude/project/meta/rules/architecture.md - core principles (FC/IS, DDD, immutability)
Java (if designing for Java/Spring Boot):
~/.dotfiles/claude/project/java/rules/java-patterns.md - records, sealed types, Either, railway-oriented programming~/.dotfiles/claude/project/java/rules/property-testing.md - jqwik invariants
TypeScript (if designing for TypeScript/Next.js):
~/.dotfiles/claude/project/typescript/rules/typescript-patterns.md - discriminated unions, branded types, ts-pattern
