Interactive selector and router 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.
View on GitHubplugins/archetypes/skills/architecture-paradigms/SKILL.md
February 1, 2026
Select agents to install to:
npx add-skill https://github.com/athola/claude-night-market/blob/main/plugins/archetypes/skills/architecture-paradigms/SKILL.md -a claude-code --skill architecture-paradigmsInstallation paths:
.claude/skills/architecture-paradigms/## Table of Contents - [Quick Scenario Router](#quick-scenario-router) - [3-Step Selection Workflow](#3-step-selection-workflow) - [Available Paradigm Skills](#available-paradigm-skills) - [Integration with Other Skills](#integration-with-other-skills) - [Exit Criteria](#exit-criteria) # Architecture Paradigm Router This skill helps you **select** the right architecture paradigm(s) for your system, then **routes** you to the specific paradigm skill for implementation details. ## Quick Scenario Router Match your needs to the recommended paradigm: | Your Scenario | Primary Paradigm | Load Skill | |---------------|------------------|------------| | **Enterprise app with multiple teams** | Microservices or Modular Monolith | `architecture-paradigm-microservices` or `architecture-paradigm-modular-monolith` | | **Complex business rules & testing** | Functional Core, Imperative Shell | `architecture-paradigm-functional-core` | | **Real-time/event processing** | Event-Driven Architecture | `architecture-paradigm-event-driven` | | **Legacy system modernization** | Hexagonal (Ports & Adapters) | `architecture-paradigm-hexagonal` | | **Cloud-native/bursty workloads** | Serverless | `architecture-paradigm-serverless` | | **ETL/data processing pipeline** | Pipeline Architecture | `architecture-paradigm-pipeline` | | **Simple CRUD app** | Layered Architecture | `architecture-paradigm-layered` | | **Command/query separation** | CQRS + Event Sourcing | `architecture-paradigm-cqrs-es` | ## 3-Step Selection Workflow ### Step 1: Define Your Needs **Primary Concerns** (select all that apply): - **Testability**: Isolate business logic → `functional-core` or `hexagonal` - **Team Autonomy**: Independent deployment → `microservices` or `modular-monolith` - **Infrastructure Flexibility**: Swap databases/frameworks → `hexagonal` - **Real-time Scaling**: Variable loads with events → `event-driven` or `space-based` - **Simplicity**: Maintainable without complexity → `layered` or `modu