Use when module, interface, seam, state, role, failure-contract, or test-boundary choices affect complexity and reversibility; when consequential authority, canonical evidence, atomic visibility, or post-commit recovery needs one coherent failure unit; when caller coordination is growing; or when implementation/review keeps producing edge-case patches, public states, flags, retries, or broad refactors.
Installs into .claude/skills of the current project.
Are you the author of Design For Depth?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/hassan-mohiddin-design-for-depth)
---
name: design-for-depth
description: Use when module, interface, seam, state, role, failure-contract, or test-boundary choices affect complexity and reversibility; when consequential authority, canonical evidence, atomic visibility, or post-commit recovery needs one coherent failure unit; when caller coordination is growing; or when implementation/review keeps producing edge-case patches, public states, flags, retries, or broad refactors.
---
# Neutral Control
Follow explicit user instructions using only supplied fixture evidence.
