Architecture paradigm selection and implementation planning.
Archetypes helps you choose the right architecture for your system. It provides an interactive paradigm selector and detailed implementation guides for 13 architectural patterns.
/plugin install archetypes@claude-night-market
Skill Description When to Use
architecture-paradigmsInteractive paradigm selector Choosing architecture for new systems
Skill Architecture Best For
architecture-paradigm-layeredN-tier Simple web apps, internal tools architecture-paradigm-hexagonalPorts & Adapters Infrastructure independence architecture-paradigm-microservicesDistributed services Large-scale enterprise architecture-paradigm-event-drivenAsync communication Real-time processing architecture-paradigm-serverlessFunction-as-a-Service Event-driven with minimal infra architecture-paradigm-pipelinePipes-and-filters ETL, media processing architecture-paradigm-cqrs-esCQRS + Event Sourcing Audit trails, event replay architecture-paradigm-microkernelPlugin-based Minimal core with extensions architecture-paradigm-modular-monolithInternal boundaries Module separation without distribution architecture-paradigm-space-basedData-grid High-scale stateful workloads architecture-paradigm-service-basedCoarse-grained SOA Modular without microservices architecture-paradigm-functional-coreFunctional Core, Imperative Shell Superior testability architecture-paradigm-client-serverClient-server Clear client/server responsibilities
Skill(archetypes:architecture-paradigms)
# Claude will:
# 1. Ask about your requirements
# 2. Evaluate trade-offs
# 3. Recommend paradigms
# 4. Provide implementation guidance
# Get specific paradigm details
Skill(archetypes:architecture-paradigm-hexagonal)
# Returns:
# - Core concepts
# - When to use
# - Implementation patterns
# - Example code
# - Trade-offs
Level Paradigms
Low Layered, Client-Server Medium Modular Monolith, Service-Based, Functional Core High Microservices, Event-Driven, CQRS-ES, Space-Based
Team Recommended
1-3 Layered, Functional Core, Modular Monolith 4-10 Hexagonal, Service-Based, Pipeline 10+ Microservices, Event-Driven
Need Paradigms
Single server Layered, Modular Monolith Horizontal Microservices, Serverless Extreme Space-Based, Event-Driven
The paradigm selector evaluates:
Team size and structure Scalability requirements Deployment constraints Data consistency needs Development velocity priorities Operational maturity
## Hexagonal Architecture (Ports & Adapters)
### Core Concepts
- Domain logic at center
- Ports define interfaces
- Adapters implement ports
- Infrastructure is pluggable
### When to Use
- Need to swap databases/frameworks
- Test-driven development focus
- Long-lived applications
- Multiple integration points
### Structure
src/
├── domain/ # Pure business logic
│ ├── models/
│ └── services/
├── ports/ # Interface definitions
│ ├── inbound/
│ └── outbound/
└── adapters/ # Implementations
├── web/
├── persistence/
└── external/
### Trade-offs
+ Easy testing via port mocking
+ Framework-agnostic domain
+ Clear dependency direction
- More initial structure
- Learning curve
Start Simple : Begin with layered, evolve as neededMatch Team : Don’t use microservices with a small teamConsider Ops : Complex architectures need operational maturityPlan Evolution : Design for change, not perfection
Start
|
v
Simple CRUD? --> Yes --> Layered
|
No
|
v
Need testability? --> Yes --> Functional Core or Hexagonal
|
No
|
v
High scale? --> Yes --> Event-Driven or Space-Based
|
No
|
v
Multiple teams? --> Yes --> Microservices or Service-Based
|
No
|
v
Modular Monolith
pensive : Architecture review complements paradigm selectionspec-kit : Use after paradigm selection for implementation planning