30-SECOND BRIEF
What it does—and when it fits
Codebase Design supplies a shared vocabulary for reviewing modules, interfaces, seams, adapters, leverage, locality, and testability. Its core preference is for deep modules: small, stable interfaces that hide substantial implementation detail, with deliberate seams only where they improve change isolation and AI or human navigability.
INSTALL BY AGENT
Choose your Agent
Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.
.claude/skills/codebase-design/~/.claude/skills/codebase-design/Use project scope for team sharing and personal scope across repositories. The installer defaults to project scope; add -g for personal scope.
npx skills add mattpocock/skills --skill codebase-design --agent claude-codeClaude Code discovers custom Skill folders automatically at project or personal scope.
View path evidence ↗TYPICAL WORKFLOW
A practical workflow
Evaluate module depth
Compare interface surface with the complexity hidden behind it.
Place useful seams
Find boundaries that isolate change, dependencies, and tests.
Improve codebase navigation
Use consistent structural language to make unfamiliar systems easier to reason about.
THE TRADEOFFS
Advantages and tradeoffs
Notable strengths
- This profile is manually organized around the current upstream SKILL.md workflow.
- The capability boundary remains explicitly tied to mattpocock/skills.
- Core uses, limitations, and risks are separated for pre-install review.
Limitations
- The vocabulary helps critique design but does not produce a correct architecture automatically.
- Chasing seams or abstraction too early can increase indirection and make a small system harder to change.
BEST FIT
Who it is for
Engineers reviewing codebase structure
Teams designing maintainable module boundaries
BEFORE YOU USE IT
Risks to review before use
Premature abstraction
Applying the vocabulary mechanically can create shallow wrappers, speculative adapters, and scattered logic. Demand concrete change pressure and testability gains before adding a boundary.
Upstream instruction drift
Behavior can change with upstream updates. Record the commit used for important workflows and review updates before adoption.
SECURITY
What the permission profile means
- Declared access remains governed by the current upstream SKILL.md and runtime requests.
- Treat repository files, web content, and tool output as untrusted input.
- SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.
Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.
INSIDE THE PACKAGE
Indexed files
TAGS
Manually expanded from the current upstream SKILL.md and linked source at mattpocock/skills, checked 2026-08-20. This is an original summary, not an execution result or security certification.