Shared vocabulary and principles for designing deep modules with narrow interfaces. Use when designing module interfaces, locating architectural seams, or structuring complex software.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Codebase Design
Design **deep modules**: a lot of behaviour behind a small interface, placed at a clean seam, testable through that interface. Use this language and these principles wherever code is being designed or restructured. The aim is leverage for callers, locality for maintainers, and testability for everyone.
## Glossary
Use these terms exactly: don't substitute "component," "service," "API," or "boundary." Consistent language is the whole point.
**Module**: anything with an interface and an implementation. Deliberately scale-agnostic: a function, class, package, or tier-spanning slice. _Avoid_: unit, component, service.
**Interface**: everything a caller must know to use the module correctly: the type signature, but also invariants, ordering constraints, error modes, required configuration, and performance characteristics. _Avoid_: API, signature (too narrow, they refer only to the type-level surface).
…
The line at the top of this page pins the label git:20261016.0f9b29d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_s6i7mbwvb63fsfaf
GET https://markdownregistry.com/api/v1/resolve?ref=saifallah-star/aegis/codebase-design
GET https://markdownregistry.com/api/v1/blob/de26043ccbdf5487a42d0d08d3ce75dd4e541e0f33de74662f50e638141e3edd
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
saifallah-star/aegis · .agents/skills/ask-matt/SKILL.md · Router to help choose the right skill or engineering workflow for your situation. Use when the user asks for guidance…
saifallah-star/aegis · .agents/skills/diagnosing-bugs/SKILL.md · Disciplined diagnosis loop for hard bugs and performance regressions: reproducible test -> isolate -> hypothesis ->…
saifallah-star/aegis · .agents/skills/domain-modeling/SKILL.md · Actively build and sharpen a project's ubiquitous domain language, glossary, and Architectural Decision Records (ADRs)…
saifallah-star/aegis · .agents/skills/grill-me/SKILL.md · Interview the user relentlessly about a plan, idea, or decision until all branches of the design tree are settled. Use…
saifallah-star/aegis · .agents/skills/grill-with-docs/SKILL.md · Relentless interview session to stress-test and clarify a design or plan while creating GLOSSARY.md and ADRs inline…
saifallah-star/aegis · .agents/skills/grilling/SKILL.md · Core interviewing primitive that maps decisions into a branching design tree, working the frontier one round of…
saifallah-star/aegis · .agents/skills/handoff/SKILL.md · Serialize the active conversation context into a structured handoff document for another agent or future session to…
saifallah-star/aegis · .agents/skills/implement-spec/SKILL.md · Execute an entire spec on an integration branch by coordinating implementer subagents across a ticket task graph…
saifallah-star/aegis · .agents/skills/implement/SKILL.md · Build out work based on a spec or tickets by driving TDD at pre-agreed seams and closing with code review. Use when the…
saifallah-star/aegis · .agents/skills/improve-codebase-architecture/SKILL.md · Scan a codebase for module deepening and refactoring opportunities, generate an interactive HTML report, and grill…
saifallah-star/aegis · .agents/skills/pr/SKILL.md · Format structured pull request bodies with concise visuals, test verifications, and blast-radius analysis. Use when…
librechat-ai/librechat · .claude/skills/codebase-design/SKILL.md · Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find…
danny-avila/librechat · .claude/skills/codebase-design/SKILL.md · Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find…
dcouple/pane · main/src/services/paneChatBundle/skills/codebase-design/SKILL.md · Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find…
greenfield-inc/pane · main/src/services/paneChatBundle/skills/codebase-design/SKILL.md · Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/codebase-design/SKILL.md · Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find…
mxyhi/ok-skills · codebase-design/SKILL.md · Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find…
asymmetric-al/core · .agents/skills/codebase-design/SKILL.md · Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find…