Use before implementing or refactoring software when the task requires designing module boundaries, APIs, layers, abstractions, services, repositories, adapters, or architecture. Helps coding agents reduce total system complexity by creating deep modules, hiding implementation knowledge, avoiding leakage and pass-through APIs, comparing alternative designs, documenting interfaces before coding, and critiquing existing architecture.
90
90%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Reusable coding-agent skill for designing software modules before implementation.
Main entry point: SKILL.md.
Supporting files:
references/decision-rules.md — detailed rules for interfaces, information hiding, leakage, pass-through APIs, layering, splitting/merging, and error design.references/review-checklist.md — design review questions and final gates.templates/design-brief.md — pre-implementation design brief template.templates/architecture-critique.md — architecture critique template.examples/module-design-examples.md — good and bad module design examples.