design-deep-modules
/design-deep-modules
Design or compare concrete high-leverage module boundaries with small stable interfaces, hidden complexity, explicit seams, adapters, locality, and reversible migration. Use when the request asks for boundary or interface design; not for whole-architecture audits or requests that explicitly defer new module-boundary design.
- Author
- woliveiras ↗
- Repository
- baseline ↗
- Licence
- MIT
- Last repository change
- 19.08.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 19.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Design or compare concrete high-leverage module boundaries with small stable interfaces, hidden complexity, explicit seams, adapters, locality, and reversible migration. Use when the request asks for boundary or interface design; not for whole-architecture audits or requests that explicitly defer new module-boundary design.
Original author description
Design or compare concrete high-leverage module boundaries with small stable interfaces, hidden complexity, explicit seams, adapters, locality, and reversible migration. Use when the request asks for boundary or interface design; not for whole-architecture audits or requests that explicitly defer new module-boundary design.
How it works
SKILL.md has no level-two headings · 19 lines, 301 words
SKILL.md preview
--- name: design-deep-modules description: Design or compare concrete high-leverage module boundaries with small stable interfaces, hidden complexity, explicit seams, adapters, locality, and reversible migration. Use when the request asks for boundary or interface design; not for whole-architecture audits or requests that explicitly defer new module-boundary design. --- # Design Deep Modules Use depth, seams, adapters, leverage, locality, and the deletion test as diagnostics, not slogans. This workflow owns boundary options and their trade-offs. It does not select among material viable options when that choice requires a separate decision owner; hand those options to `decision-framework`. 1. Start from governing behavior, invariants, callers, state ownership, side effects, failure modes, change history, contracts, and tests. 2. Apply the deletion test: identify which caller concepts and coordination disappear if the module is removed. Pass-through indirection with no hidden decision has little depth. 3. For consequential boundaries, load [boundary options](./references/boundary-options.md) and compare at least two materially different interfaces under the same scenarios. 4. Prefer small interfaces that let callers express intent while the module owns relevant coordination, dependency lifecycle, translation, and failure handling. 5. Put external mechanisms behind adapters; keep domain policy out of translation layers. Hide dependencies whose choices belong inside the module, but expose obligations callers truly own. 6. Evaluate test coupling. Protect behavior at the boundary; retain internal tests only for complex invariants that are uneconomical to observe externally. 7. Plan reversible slices, compatibility, rollback, evidence seams, and authority before irreversible operations. 8. Use Mermaid only when three or more modules, dependencies, or migration steps are hard to understand in prose. Show dependency direction, seams, and proposed change; never generate HTML. 9. Finish design-only work with a concise completion report that mirrors the durable artifact: selected boundary, alternatives and trade-offs, external translation seam, reversible validation or migration, unresolved decisions, and whether implementation occurred. Record trade-offs in the governing input only when changing that artifact is explicitly authorized. Otherwise use the requested design/decision artifact or the response. Create an ADR only when the repository's decision threshold is met. Draw operational rules from recognized modular-design references; citations never substitute for repository evidence.
Files in this package (3)
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
- references/boundary-options.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · woliveiras/baseline | 86 | MIT |
| theonly1me/shadowclone | 100 | MIT |
| laurigates/claude-plugins | 90 | MIT |
Database snapshot: 13.11.2026 · package version e02821f53675 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100deep-module-design
Design deep modules with small interfaces and rank shallow, pass-through or leaky code for deepening. Use when designing a module interface, improving codebase architecture, or making code easier to test. - 100api-and-interface-design
Stable API and interface design patterns. Use when designing REST/GraphQL endpoints, module boundaries, type contracts between modules or frontend/backend, or changing public interfaces. - 100api-and-interface-design
Stable API and interface design patterns. Use when designing REST/GraphQL endpoints, module boundaries, type contracts between modules or frontend/backend, or changing public interfaces. - 100module-boundary-design
模块边界设计。基于已完成的功能设计(SR-design),识别受影响模块,逐模块定义边界(职责、上游依赖、下游暴露),绘制模块交互时序,并通过对抗式审查发现边界冲突(职责泄漏、循环依赖、边界破坏、重复能力)。输出 module-boundary-design.md。用于AAW工作流步骤3。Use when the user asks for 模块边界设计、module-boundary-design。 - 100api-and-interface-design
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend. - 95api-and-interface-design
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.