Design and evaluate module interfaces, depth, seams, adapters, locality, and testability. Use when deciding what a module should hide, what callers should know, where dependencies should vary, whether an abstraction earns its cost, or how to make one subsystem easier to test and modify. Also use when another skill needs consistent 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
Concentrate complexity behind useful interfaces. A good module gives callers
substantial capability while keeping knowledge, change, bugs, and verification
local.
When another skill loads this one, apply the vocabulary and analysis below inside
that skill's workflow and output format. When invoked directly, complete the full
workflow and return the module-design report.
## Workflow
### 1. Frame the module
Identify the module under review, its responsibility, callers, dependencies, public
entry points, observable behavior, and constraints. A module may be a function,
class, component, package, service, feature, or tier-spanning slice.
Use the repository's framework terms for concrete artifacts and *module* for their
design role.
**Complete when:** the module, its callers, its current contract, and the desired
outcome are explicit.
### 2. Map interface burden
List everything a caller must know to use the module correctly:
- operations and data shapes;
- invariants and valid ordering;
- errors and recovery responsibilities;
- configuration and lifecycle;
- performance or concurrency characteristics;
…
The line at the top of this page pins the label git:20261006.c9355ee, 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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (5992 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
kriscard/skills · 14 stars · license MIT · pushed 2026-10-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6ze27i75kpdo42a7
GET https://markdownregistry.com/api/v1/resolve?ref=kriscard/skills/codebase-design
GET https://markdownregistry.com/api/v1/blob/f6401e792fd09d4b8667fe4ae8f6fec75bb0d66b27cbfb9a638405bba9119281
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.
kriscard/skills · skills/dev/analyze-repo/SKILL.md · Generate an evidence-backed visual architecture and technical-debt audit for an entire repository.
kriscard/skills · skills/dev/pr-review/SKILL.md · Bug-first, evidence-only review of a pull request or branch-versus-base diff. Use when the user explicitly asks to…
kriscard/skills · skills/dev/react-hook-form/SKILL.md · Build and modify forms that use React Hook Form or whose project conventions require it. Use when implementing…
kriscard/skills · skills/dev/refactor/SKILL.md · Behavior-preserving code refactoring. Use when the user asks to simplify complex or duplicated code, improve naming…
kriscard/skills · skills/dev/research/SKILL.md · Current, source-grounded implementation research for libraries, frameworks, SDKs, and APIs. Use when coding depends on…
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…
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…
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…
