What problem does it solve? Teams struggle to decide where to draw module boundaries, when to split or merge services, and how to review architecture for coupling problems without framework-specific rules. This Skill provides technology-agnostic principles and workflows for designing, reviewing, and auditing modular systems. ## Core Features & Use Cases - Ten Modularity Principles: Covers well-defined boundaries, composability, state isolation, explicit contracts, failure containment, and observability, with per-principle agent rules in references/principles.md. - Bounded Context Workflow: Step-by-step process for scoping new modules, defining public contracts, state ownership, and integration consistency. - Split/Merge Decision Criteria: A six-criteria test (language, rate of change, scale, consistency, ownership, pain signals) to decide when to split or merge modules. - Compliance Review Signals: P0/P1/P2 severity heuristics for auditing dependency leaks, reach-through persistence, and cascading failures. - Use Case: When reviewing whether a growing monolith's billing and inventory code should become separate services, apply the six-criteria test and compliance signals to produce a reasoned recommendation. ## Quick Start Ask the agent to review your module structure or evaluate whether a specific part of the codebase should be split into its own bounded context.
