Design or improve module boundaries and public interfaces. Use for architecture, testability, or shared deep-module concepts.
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 concepts to clarify the design while preserving the project’s established glossary. Translate module/interface terminology to component, service, API, or boundary when that is clearer in context.
**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:20261011.ef64499, 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_baqg7yqbhppvmbbc
GET https://markdownregistry.com/api/v1/resolve?ref=transitive-bullshit/skills/codebase-design
GET https://markdownregistry.com/api/v1/blob/6feff4d41f186855dfeb9179f1f2d531644445b5ce1a486aaeb7cd4b9ebb151a
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.
transitive-bullshit/skills · provenance/history/2026-10-11-removed/resolving-merge-conflicts/SKILL.md · Use when you need to resolve an in-progress git merge/rebase conflict.
transitive-bullshit/skills · provenance/upstream/auto-research/skill/SKILL.md · Run fast, progressive experiments to map tunable parameters and their effects. Use when optimizing code, prompts…
transitive-bullshit/skills · provenance/upstream/better-colors/SKILL.md · Helps you build and check a color system for your project. It generates palettes, names semantic tokens, converts…
transitive-bullshit/skills · provenance/upstream/better-layout/SKILL.md · Helps with grouping, alignment, reading order, responsive structure and room for translated text, so a layout holds up…
transitive-bullshit/skills · provenance/upstream/better-typography/SKILL.md · Sets and reviews how text renders in your product, from the type scale and spacing to font features, wrapping…
transitive-bullshit/skills · provenance/upstream/better-ui/SKILL.md · Polishes the surfaces, icons and motion in your project with exact values for border radius, optical alignment…
transitive-bullshit/skills · provenance/upstream/better-writing/SKILL.md · Writes and reviews your interface copy, from labels and errors to empty states and confirmations, so it matches your…
transitive-bullshit/skills · provenance/upstream/claude/skill/SKILL.md · Use Claude Code as an independent `claude -p` subagent when the user explicitly asks for Claude, wants a second-agent…
transitive-bullshit/skills · provenance/upstream/codebase-design/skill/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…
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…