Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
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:20260622.889f27e, 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_nssrnkjdpfv5qorq
GET https://markdownregistry.com/api/v1/resolve?ref=coder/agent-tty/codebase-design
GET https://markdownregistry.com/api/v1/blob/ab24353b4db20400b6d2ffe752a93770ec53adde072edc6cf0bb65caf4c5c427
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.
coder/agent-tty · .agents/skills/diagnosing-bugs/SKILL.md · Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports…
coder/agent-tty · .agents/skills/domain-modeling/SKILL.md · Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous…
coder/agent-tty · .agents/skills/grill-with-docs/SKILL.md · A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
coder/agent-tty · .agents/skills/grilling/SKILL.md · Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building…
coder/agent-tty · .agents/skills/improve-codebase-architecture/SKILL.md · Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you…
coder/agent-tty · .agents/skills/improve/SKILL.md · Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER…
coder/agent-tty · .agents/skills/release-maintainer/SKILL.md · Internal maintainer SOP for version bumps, release PRs, tagging, publishing, and post-publish verification in this…
coder/agent-tty · .agents/skills/to-issues/SKILL.md · Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet…
coder/agent-tty · .agents/skills/to-prd/SKILL.md · Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of…
coder/agent-tty · .agents/skills/triage/SKILL.md · Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write…
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…
