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:20260923.15c9348, 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_4nvix6tpy3xqrwhs
GET https://markdownregistry.com/api/v1/resolve?ref=asymmetric-al/core/codebase-design
GET https://markdownregistry.com/api/v1/blob/5f0f9a507f74a9c709bd45f9034f64a46bc10395270bcc564b15dbf428bddf35
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.
asymmetric-al/core · .agents/skills/accessibility-review/SKILL.md · Audit and fix accessibility in Core UI. Use when changing or reviewing buttons, links, forms, validation, dialogs…
asymmetric-al/core · .agents/skills/agent-browser/SKILL.md · Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages…
asymmetric-al/core · .agents/skills/agent-email-inbox/SKILL.md · Use when building any system where email content triggers actions — AI agent inboxes, automated support handlers…
asymmetric-al/core · .agents/skills/anim/SKILL.md · Tasteful, subtle web UI animation following Emil Kowalski / animations.dev principles. Use when adding or reviewing…
asymmetric-al/core · .agents/skills/animate/SKILL.md · Build an animation from scratch, making the decisions in the order that determines whether it feels right — should it…
asymmetric-al/core · .agents/skills/animation-vocabulary/SKILL.md · Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the…
asymmetric-al/core · .agents/skills/api-design-principles/SKILL.md · Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight…
asymmetric-al/core · .agents/skills/apple-design/SKILL.md · Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing…
asymmetric-al/core · .agents/skills/ask-sonner/SKILL.md · Guide to Sonner, the React toast library — install and wire up the Toaster, pick the right toast() call, promise and…
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…
oyadotai/oya-browser · .claude/skills/codebase-design/SKILL.md · This skill should be used when designing a module interface, reducing coupling, choosing dependency seams, improving…
