| name | architecture-paradigms |
| description | Interactive selector and implementation planner for architecture paradigms.
Triggers: architecture selection, pattern comparison, system design, ADR creation,
architecture decision, paradigm evaluation, new system architecture, architecture
planning, which architecture, compare architectures
Use when: selecting architecture patterns for new systems, comparing paradigm
trade-offs, creating architecture decision records, evaluating architecture fit
for team size and domain complexity, planning implementation roadmaps
DO NOT use when: implementing a specific known paradigm - use the specific
architecture-paradigm-* skill (hexagonal, layered, microservices, etc.) instead.
DO NOT use when: reviewing existing architecture - use architecture-review instead.
Use this skill BEFORE making architecture decisions. Check even if unsure about needs.
|
| version | 1.0.0 |
| category | architecture-decision |
| tags | ["architecture","patterns","selection","implementation","adr"] |
| dependencies | ["architecture-paradigm-functional-core","architecture-paradigm-hexagonal","architecture-paradigm-cqrs-es","architecture-paradigm-event-driven","architecture-paradigm-layered","architecture-paradigm-modular-monolith","architecture-paradigm-microkernel","architecture-paradigm-microservices","architecture-paradigm-service-based","architecture-paradigm-space-based","architecture-paradigm-pipeline","architecture-paradigm-serverless","architecture-paradigm-client-server"] |
| tools | ["paradigm-selector","implementation-planner","compatibility-checker"] |
| usage_patterns | ["paradigm-selection","architecture-review","implementation-planning","adr-creation"] |
| complexity | intermediate |
| estimated_tokens | 560 |
Architecture Paradigm Selector & Implementation Planner
Quick Start
For decisions: Jump to Common Scenarios (below) or use the selection matrix.
For planning: Complete the 3-step workflow to generate implementation roadmaps.
Common Scenarios
Enterprise Application with Multiple Teams
Primary: Microservices or Modular Monolith
Secondary: Hexagonal for infrastructure independence
Complex Business Rules & Testing
Primary: Functional Core, Imperative Shell
Secondary: Hexagonal for external integrations
Real-time/Event Processing
Primary: Event-Driven Architecture
Secondary: CQRS + Event Sourcing for audit trails
Legacy System Modernization
Primary: Hexagonal (Ports & Adapters)
Secondary: Modular Monolith as interim step
Cloud-Native/Bursty Workloads
Primary: Serverless
Secondary: Microservices for sustained workloads
ETL/Data Processing Pipeline
Primary: Pipeline Architecture
Secondary: Event-Driven for streaming
Required TodoWrite Items
paradigms:needs-definedparadigms:paradigms-evaluatedparadigms:roadmap-created
3-Step Selection Workflow
Step 1: Define Your Needs (paradigms:needs-defined)
Primary Concerns (select all):
