codebase-designlisted
Install: claude install-skill sandbaseai/workbuddy-skill
# Codebase Design
Use this Skill when a change adds a module, moves behavior, exposes an interface, introduces an adapter, or makes a codebase harder to navigate or test. The goal is leverage for callers and locality for maintainers: a small interface should hide substantial, coherent behavior while remaining observable through that interface.
## Use a precise vocabulary
- **Module**: anything with an interface and an implementation, from a function to a package or vertical slice.
- **Interface**: every fact a caller must know, including types, invariants, ordering, errors, configuration, and performance expectations.
- **Implementation**: behavior behind the interface. Use **adapter** only for a concrete implementation that fills a varying seam.
- **Depth**: capability delivered per unit of interface the caller must learn. A deep module has a small interface and meaningful behavior behind it.
- **Seam**: the location at which behavior can be changed without editing the caller. Choosing a seam is a design decision, not a synonym for a domain boundary.
- **Leverage**: the benefit shared by many callers and tests when behavior is centralized.
- **Locality**: the ability to change, diagnose, and verify behavior in one place.
Do not call every layer an API, component, service, or boundary when the more exact term is available. Consistent vocabulary keeps design discussions and agent handoffs searchable.
## Design the smallest honest interface
Before editing, identify caller