Claude Architect Marketplace
Expert-level architecture plugins for Claude Code. Built for senior engineers who need sophisticated architectural dialogue, not templated outputs.
Philosophy
These plugins enable peer-level architectural conversations. They bring deep knowledge of:
- Domain-Driven Design: Bounded contexts, aggregates, context mapping, anti-corruption layers
- Distributed Systems: CAP/PACELC, saga patterns, event sourcing, CQRS, outbox pattern
- Cloud-Native: 12-factor apps, container patterns, service mesh, observability
- Architecture Evaluation: ATAM-style quality attribute analysis, trade-off identification, fitness functions
- Industry Standards: C4 model, ADRs (MADR format), technical specifications
All plugins use Claude Opus for the deepest architectural reasoning.
Installation
1. Add the marketplace
/plugin marketplace add CrazyMeal/claude-architect-marketplace
2. Install plugins
Install all plugins:
/plugin install architecture-design
/plugin install architecture-analysis
/plugin install diagrams-as-code
/plugin install architecture-docs
/plugin install architecture-review
Or install only what you need.
Plugins
architecture-design
Collaborative system design drawing on DDD, distributed systems theory, and evolutionary architecture.
Commands:
/design-system <name> - Full system architecture with bounded contexts, quality attributes/design-component <name> - Component design with DDD tactical patterns, integration strategies/evolve-system <requirement> - Evolve existing architecture while respecting ADRs and constraints
Agent: system-architect - Principal architect for design discussions
Knowledge includes:
- Architectural styles (microservices, event-driven, cell-based, modular monolith)
- DDD strategic and tactical patterns
- CAP/PACELC implications
- Saga patterns (orchestration vs choreography)
- 12-factor and beyond-12-factor principles
- Conway's Law and team topology considerations
architecture-analysis
Deep codebase analysis with pattern recognition and technical debt assessment.
Commands:
/analyze-codebase [dir] - Structural analysis, domain model assessment, coupling metrics/analyze-dependencies [file] - Architectural dependency analysis (not just version checking)
Agent: code-analyst - Principal engineer for reverse-engineering existing systems
Capabilities:
- Coupling analysis (afferent/efferent, instability)
- Pattern and anti-pattern detection
- Technical debt categorization (reckless/prudent, deliberate/inadvertent)
- Bounded context identification from code
- Evolution readiness assessment
diagrams-as-code
C4 model diagrams with proper abstraction discipline.
Commands:
/diagram <type> [format] - Architecture diagrams with purpose-driven selection/c4-diagram <level> - C4 diagrams: Context, Container, Component, plus Deployment and Dynamic/diagram-from-code <type> [dir] - Generate diagrams from existing code
Agent: diagram-assistant - Architecture visualization expert
C4 Knowledge:
- Abstraction levels and when to use each
- Notation standards (PlantUML C4 library, Mermaid)
- Supplementary diagrams (deployment, dynamic)
- Structurizr DSL for architecture-as-code
Formats: PlantUML (recommended for C4), Mermaid (docs), D2 (presentations)
architecture-docs
Industry-standard documentation following best practices.
Commands:
/adr <title> - MADR format with decision drivers, alternatives, consequences/tech-spec <feature> - Specification with quality attributes, operational concerns, risks/rfc <title> - Request for Comments for major proposals
Agent: technical-writer - Senior architect focused on documentation
Documentation Knowledge:
- MADR (Markdown Any Decision Record) format
- Y-statement format for decisions
- Quality attribute specifications
- C4 documentation practices
- Runbook structure
architecture-review
Rigorous evaluation using quality attribute analysis.
Commands:
/review-architecture [doc] - ATAM-inspired review with quality scenarios/risk-assessment [doc] - Comprehensive risk taxonomy and mitigation strategies/review-adr <file> - ADR quality review
Agent: architecture-reviewer - Principal architect for design evaluation
Evaluation Framework:
- Quality attribute scenarios (stimulus → response under conditions)
- Sensitivity points and trade-off points
- Risk categorization (technical, operational, organizational, external)
- Fitness function recommendations
Usage Examples
Designing with Context
"I need to design an order processing system. We're expecting
10K orders/day, need to integrate with three payment providers,
and the team has strong Go experience but limited Kafka knowledge."
