domains / families / software-engineering / codebase-design

codebase-design

authentic

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.

When to use

• designing or improving a module's interface
• finding deepening opportunities
• deciding where a seam goes
• making code more testable
• making code AI-navigable
• providing deep-module vocabulary for other skills

When not to use

• using terms like component, service, API, or boundary
• defining depth as a ratio of implementation-lines to interface-lines
• defining interface as only the TypeScript interface keyword or public methods

Skill page

Source