architecture-paradigms
Interactive selector and router for architecture paradigms
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/athola/nm-archetypes-architecture-paradigmsNight 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 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-coreorhexagonal - Team Autonomy: Independent deployment →
microservicesormodular-monolith - Infrastructure Flexibility: Swap databases/frameworks →
hexagonal - Real-time Scaling: Variable loads with events →
event-drivenorspace-based - Simplicity: Maintainable without complexity →
layeredormodular-monolith - Legacy Integration: Work with existing systems →
hexagonalormicrokernel
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
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-athola-nm-archetypes-architecture-paradigms": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
extract
Analyze a codebase and build a knowledge base of business logic, architecture, data flow, and engineering patterns. The foundation for gauntlet challenges and agent integration
discourse
>- Scan community discussion channels (HN, Lobsters, Reddit, tech blogs) for experience reports and opinions on a topic
synthesize
>- Merge, deduplicate, rank, and format research findings from multiple channels into a coherent report. Use after research agents return their results
workflow-monitor
Detect workflow failures and inefficient patterns, then create GitHub issues for improvement via /fix-workflow
architecture-paradigm-hexagonal
Hexagonal (Ports and Adapters) architecture isolating domain logic from infrastructure