Modular Design Principles

by tech-leads-club120b67676388No licenseListed Oct 8, 2026Updated Oct 8, 2026

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).

Instructions onlySoftware Development
  1. 120b67676388Currentcommit 120b676Published Oct 8, 2026

Source and attribution

Source:tech-leads-club/agent-skillsinpackages/skills-catalog/skills/(architecture)/modular-design-principlesat commit120b676

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal