Architecture Designer
Skill Verified ActiveUse when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.
To assist users in designing new high-level system architectures, reviewing existing ones, and making informed architectural decisions, producing structured documentation and well-reasoned trade-offs.
Features
- Create architecture diagrams (Mermaid)
- Write Architecture Decision Records (ADRs)
- Evaluate technology trade-offs
- Plan for system scalability
- Select architectural patterns
Use Cases
- Designing new system architecture from scratch
- Reviewing and evaluating existing system designs
- Making informed architectural decisions for new features or systems
- Documenting key architectural choices using ADRs
Non-Goals
- Detailed code-level design patterns
- Database-only design tasks
- Over-engineering for hypothetical scale
- Ignoring operational costs or security considerations
Installation
First, add the marketplace
/plugin marketplace add jeffallan/claude-skills/plugin install claude-skills@fullstack-dev-skillsQuality Score
VerifiedSimilar Extensions
System Design
99Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "system design interview", "capacity planning", or "distributed architecture". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.
Pathfinder
100Map a codebase into feature-grouped flowcharts, identify duplicated concerns across features, and propose a unified architecture. Use when asked to "find the ideal path," unify duplicated systems, or audit architecture before a refactor. Emits a proposed unified flowchart plus per-system /make-plan prompts.
Architecture Decision Records
99Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
Agent Arch System Design
98Agent skill for arch-system-design - invoke with $agent-arch-system-design
Review Software Architecture
97Review software architecture for coupling, cohesion, SOLID principles, API design, scalability, and technical debt. Covers system-level evaluation, architecture decision record review, and improvement recommendations. Use when evaluating a proposed architecture before implementation, assessing an existing system for scalability or security, reviewing ADRs, performing a technical debt assessment, or evaluating readiness for significant scale-up.
V3 Ddd Architecture
100Domain-Driven Design architecture for claude-flow v3. Implements modular, bounded context architecture with clean separation of concerns and microkernel pattern.