modular-design-principles

SKILLWorkflowcommunity
v0.0.0tech-leads-clubNOASSERTIONUpdated 2mo agoSource →

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 modul

Community-submitted skill. Not yet reviewed by the Forge team. Full prompt content may not be available.Request review →
5kRepo stars
1Clients
1Formats
2mo agoLast update
Skill
Authortech-leads-club
Version0.0.0
LicenseNOASSERTION
CategoryWorkflow
Formatsskill.md
PromptOpen (see Prompt tab)
Compatibility
Claude✓ Supported
Cursor—
Copilot—
ChatGPT—
Gemini—
About

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 th

Keywords
skillclaude

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.

Topics

Related in design tools