Menu
Shared vocabulary for designing deep modules — depth, seams, adapters, testability. Inspirado por mattpocock/skills.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | codebase-design |
| description | Shared vocabulary for designing deep modules — depth, seams, adapters, testability. Inspirado por mattpocock/skills. |
| version | 1.0.0 |
| metadata | {"source":"github.com/mattpocock/skills"} |
Design deep modules: a lot of behaviour behind a small interface, placed at a clean seam, testable through that interface.
Use these terms exactly:
Module — anything with an interface and an implementation. Scale-agnostic: function, class, package, or tier-spanning slice.
Interface — everything a caller must know to use the module correctly: type signature, invariants, ordering constraints, error modes, config, performance characteristics.
Implementation — what's inside a module, its body of code.
Depth — leverage at the interface: amount of behaviour per unit of interface the caller must learn. A module is deep when lots of behaviour sits behind a small interface, shallow when the interface is nearly as complex as the implementation.
Seam (Michael Feathers) — a place where you can alter behaviour without editing in that place.
Adapter — a concrete thing that satisfies an interface at a seam.
Leverage — what callers get from depth: more capability per unit of interface learned.
Locality — what maintainers get from depth: change concentrates in one place.
Deep module: Small Interface + Lots of Implementation ✅
Shallow module: Large Interface + Thin Implementation ❌
O módulo está desenhado com vocabulário consistente (module, interface, depth, seam), e a interface é menor que a implementação.
Resolver conflitos de merge/rebase de forma estruturada. Inspirado por mattpocock/skills.
Disposable experiments to validate an idea before committing to a build. Validate feasibility, compare approaches, surface unknowns. Also covers quick prototypes to answer a single design question (logic or UI).
Evolve prompts, code, and configurations through reflective optimization with AI feedback.
Regression testing patterns for AI-assisted development. Sandbox/production path parity, response shape contracts, data completeness, and patterns to catch AI blind spots.
REST API design patterns — resource naming, HTTP semantics, status codes, versioning, pagination, error handling, rate limiting, and OpenAPI specs. Use when designing or reviewing REST APIs.
Guard your API: JWT, OAuth 2.0, RBAC, sessions, and API key patterns for secure authentication and authorization.