MVPavan/via / .claude/skills/codebase-design
codebase-design
VerifiedUse for substantive module-interface, encapsulation, or testability decisions. Skip ordinary code explanations and cosmetic refactors.
| File | Kind | Size |
|---|---|---|
| DEEPENING.md | markdown | 1.1 KB |
| DESIGN-IT-TWICE.md | markdown | 720 B |
| SKILL.md | skill md | 2.0 KB |
| agents/openai.yaml | config | 42 B |
SKILL.md
View on GitHub---
name: codebase-design
description: Use for substantive module-interface, encapsulation, or testability decisions. Skip ordinary code explanations and cosmetic refactors.
---
# Codebase Design
Design interfaces that hide useful complexity and concentrate change. Apply this
lens to real interface or module decisions, not every explanation of code.
## Vocabulary
- **Module:** an interface and its implementation, at a useful scale.
- **Interface:** what callers must know, including invariants, ordering, errors,
configuration and performance constraints, not just type signatures.
- **Depth:** useful behavior hidden behind a manageable interface.
- **Seam:** a place where behavior can vary without changing its callers.
- **Adapter:** a concrete implementation filling a role at that seam.
- **Locality:** related knowledge, changes and checks stay together.
Use established project vocabulary, including API, service or boundary where
precise. These definitions aid reasoning rather than replacing the domain glossary.
## Design checks
Ask what callers gain, what complexity disappears from them, and what knowledge
still leaks through. If deleting a layer merely removes forwarding, question its
value; if it spreads complexity across callers, the layer may be earning its keep.
An interface can be justified by encapsulation, ownership or a present testing
need even with one implementation. Additional adapters are evidence of variation,
not a universal prerequisite. Internal seams and focused internal tests are valid;
do not expose internals merely to satisfy a testing rule.
Prefer explicit dependencies and pure calculations where they clarify behavior;
side effects are legitimate responsibilities when isolated and well specified.
Preserve compatibility and operational constraints when deepening a module.
For dependency-oriented deepening, use `DEEPENING.md`. For a consequential interface
choice with multiple credible designs, optionally use `DESIGN-IT-TWICE.md`;
ordinary design decisions do not require multiple agents or variants.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |