Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/architecture-paradigms
Selects and routes to the right architecture paradigm.
Passed 23 of 25 test cases with the skill, and 4 of 25 without it.
and 19 more in the full report
19 fixed4 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 19 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have selected Modular Monolith as our paradigm using the paradigm router. Which command should we run next if we want to create a detailed implementation task breakdown?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends using /writing-plans for detailed task breakdowns. | Missed | Passed |
The instructions your model reads when the skill loads.
pensive:architecture-review)This skill helps you select the right architecture paradigm(s) for your system, then routes you to the specific paradigm skill for implementation details.
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 and Event Sourcing | architecture-paradigm-cqrs-es |
| Rich business rules to model | Domain-Driven Design | architecture-paradigm-domain-driven |
One of these is not like the others. Domain-Driven Design answers "what are the concepts and what do we call them." The rest answer "where does the code go." DDD composes with a structural paradigm (commonly layered, hexagonal, or modular monolith) rather than competing with it, so selecting it does not mean deselecting one of the others.
Primary Concerns (select all that apply):
functional-core or hexagonalmicroservices or modular-monolithhexagonaltest cases passed, vs 4 / 25 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.