nw-architectural-styles-tradeoffs
Architectural style selection decision matrices, trade-off analysis, structural enforcement rules, and combination patterns. Load when choosing or evaluating architecture styles.
npx skills add majiayu000/claude-skill-registry --skill nw-architectural-styles-tradeoffs --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Architectural Styles: Selection and Trade-offs ## Style Selection Decision Tree Start here. Answer the dominant driver, follow to recommended style. ``` Is the domain complex with rich business rules? YES -> Do you need infrastructure independence and high testability? YES -> Hexagonal / Clean / Onion (functionally equivalent, different terminology) NO -> Is the domain well-understood with clear module boundaries? YES -> Modular Monolith (single deployment, structured boundaries) NO -> Layered Architecture (simple, well-known, fast to start) NO -> Is this a feature-heavy application with independent feature teams? YES -> Vertical Slice (per-feature organization, CQRS-friendly) NO -> Do you need independent deployment and scaling per capability? YES -> Can the team handle distributed system operational complexity? YES -> Microservices NO -> Modular Monolith (extract to services later) NO -> Is the primary concern async workflows or event-driven processing? YES -> Event-Driven Architecture NO -> Is this a data processing pipeline? YES -> Pipe and Filter NO -> Layered Architecture (sensible default) ``` ## Cross-Cutting Comparison Matrix | Style | Dep. Direction | Organization | Dep
- Style Selection Decision Tree
- Cross-Cutting Comparison Matrix
- When-to-Use / When-NOT Decision Matrix
- Hexagonal / Clean / Onion (equivalent patterns, different names)
- Vertical Slice
- Microservices
- Modular Monolith
- Event-Driven / CQRS
- Pipe and Filter
- Combination Patterns
- Enforceable Structural Rules
- Hexagonal
- Architecture Enforcement Tooling
- Python Example (import-linter)
What does the nw-architectural-styles-tradeoffs skill do?
Architectural style selection decision matrices, trade-off analysis, structural enforcement rules, and combination patterns. Load when choosing or evaluating architecture styles.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill nw-architectural-styles-tradeoffs --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.