principle-boundary-discipline

Originally fromcursor/plugins
Installation
SKILL.md

Boundary Discipline

Validate, narrow types, and handle errors where data crosses a system boundary (CLI args, config files, external APIs, network). Inside, trust the types: no re-validation and no redundant nil checks. Parse raw data into domain types at the boundary, and keep transport and framework types out of the public surface. Business logic lives in pure functions with no framework dependencies. The shell that calls them is thin.

Two tests. Is this data crossing a boundary right now? If not, the validation is redundant. Can this be a pure function the shell just calls? If yes, extract it.

For module/interface reasoning invoke /codebase-design; for accepted project terminology, relationships, or ownership changes invoke /domain-modeling and reconcile the canonical project artifacts.

Installs
65
GitHub Stars
1
First Seen
Oct 26, 2026