architecture-paradigms

## When NOT To Use - The paradigm is already chosen, so go straight to that paradigm's skill - Reviewing an existing design against its ADRs (use `pensive:architecture-review`) ## 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-pi...