Night Market Skill — ported from claude-night-market/archetypes. For the full experience with agents, hooks, and commands, install the Claude Code plugin.

Table of Contents#

• Quick Scenario Router
• 3-Step Selection Workflow
• Available Paradigm Skills
• Integration with Other Skills
• 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 ScenarioPrimary ParadigmLoad SkillEnterprise app with multiple teamsMicroservices or Modular Monolitharchitecture-paradigm-microservices or architecture-paradigm-modular-monolithComplex business rules & testingFunctional Core, Imperative Shellarchitecture-paradigm-functional-coreReal-time/event processingEvent-Driven Architecturearchitecture-paradigm-event-drivenLegacy system modernizationHexagonal (Ports & Adapters)architecture-paradigm-hexagonalCloud-native/bursty workloadsServerlessarchitecture-paradigm-serverlessETL/data processing pipelinePipeline Architecturearchitecture-paradigm-pipelineSimple CRUD appLayered Architecturearchitecture-paradigm-layeredCommand/query separationCQRS and Event Sourcingarchitecture-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 modular-monolith
• Legacy Integration: Work with existing systems → hexagonal or microkernel

System Context:

• Team Size: < 5 → Layered/Functional Core | 5-15 → Modular Monolith | 15-50 → Microservices | 50+ → Microservices/Space-Based
• Domain Complexity: Simple → Layered | Moderate → Hexagonal/Modular Monolith | Complex → Functional Core/CQRS | Highly Complex → Microservices/Event-Driven

Step 2: Evaluate Paradigms#

Based on your needs from Step 1, review these options:

For Testability & Business Logic

• Load architecture-paradigm-functional-core - Isolates business logic from infrastructure
• Load architecture-paradigm-hexagonal - Clear domain/infrastructure boundaries

For Team Autonomy

• Load architecture-paradigm-microservices - Independent deployment and scaling
• Load architecture-paradigm-modular-monolith - Team autonomy without distributed complexity

For Infrastructure Flexibility

• Load architecture-paradigm-hexagonal - Swap infrastructure without domain changes

For Simplicity & Maintainability

• Load architecture-paradigm-layered - Simple, well-understood separation

For Real-time Event Processing

• Load architecture-paradigm-event-driven - Scalable, decoupled processing
• Load architecture-paradigm-space-based - In-memory data grids for linear scalability

For Legacy Integration

• Load architecture-paradigm-microkernel - Plugin architecture for extensible platforms
• Load architecture-paradigm-hexagonal - Adapters for external systems

Step 3: Load Paradigm Skill for Implementation#

Once you've selected your paradigm(s), load the specific skill for detailed guidance:

bash

# Example: You selected Hexagonal Architecture
Skill(archetypes:architecture-paradigm-hexagonal)

The individual paradigm skill provides:

• ✅ Complete implementation guide
• ✅ ADR templates
• ✅ Migration checklist
• ✅ Code examples
• ✅ Testing strategies
• ✅ Risk assessments

Available Paradigm Skills#

ParadigmComplexityTeam SizeBest ForSkill NameFunctional CoreMediumSmall-LargeComplex business logicarchitecture-paradigm-functional-coreHexagonalMediumSmall-LargeInfrastructure changesarchitecture-paradigm-hexagonalLayeredLowSmall-MediumSimple domainsarchitecture-paradigm-layeredModular MonolithMediumMedium-LargeEvolving systemsarchitecture-paradigm-modular-monolithMicroservicesHighLargeComplex domainsarchitecture-paradigm-microservicesEvent-DrivenHighMedium-LargeReal-time processingarchitecture-paradigm-event-drivenCQRS and ESHighMedium-LargeAudit trailsarchitecture-paradigm-cqrs-esService-BasedMediumMediumCoarse-grained servicesarchitecture-paradigm-service-basedServerlessMediumSmall-MediumCloud-native/burstyarchitecture-paradigm-serverlessMicrokernelMediumSmall-MediumPlugin systemsarchitecture-paradigm-microkernelSpace-BasedHighLargeLinear scalabilityarchitecture-paradigm-space-basedPipelineLowSmall-MediumETL workflowsarchitecture-paradigm-pipelineClient-ServerLowSmallTraditional appsarchitecture-paradigm-client-server

Integration with Other Skills#

• Architecture Review: Use this skill first to select paradigms, then /architecture-review for evaluation
• Implementation Planning: Select paradigms here, then /writing-plans for detailed task breakdown
• Refactoring: Identify target paradigms here, then use paradigm-specific skills for migration strategies

Exit Criteria#

• At least one paradigm is selected with clear rationale
• Specific paradigm skill has been loaded for detailed guidance
• Ready to create ADR or implementation plan

Next Steps#

1. Load the specific paradigm skill - Use Skill(archetypes:architecture-paradigm-NAME)
2. Generate an ADR - Use the paradigm's ADR templates
3. Create implementation plan - Use paradigm's migration checklist
4. Set up monitoring - Track success metrics from paradigm guidance