Strategy & Planning
Modular Design Principles
Technology-agnostic guidance for modular systems: bounded contexts, clear boundaries, composability, state isolation, explicit contracts, failure containment, scaffolding workflows, split/merge criteria, sub-units inside a context, and compliance review signals. Use when designing or reviewing module structure, service boundaries, package layout, cross-cutting dependencies, "how should we split this?", modularity assessments, coupling between domains, greenfield context design, or architecture discussions without assuming a specific framework, language, or repository layout. Do NOT use for executing the full Patterns 1–5 repo decomposition pipeline or per-pattern inventories (use modular-decomposition), phased extraction roadmaps as the main deliverable (use decomposition-planning-roadmap), or end-to-end legacy migration strategy (use legacy-migration-planner).
- Publisher / source
- tech-leads-club/agent-skills (found on GitHub top repositories)
- Upstream record
- tech-leads-club/agent-skills
- Version
- Version 1
- Published
- Publication review
- Approved for publication
- Content fingerprint
52fe4ca680c80de2abd52773f47ba8014ff753030da6ccaa4cc1fe48d4e400f7