Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Minimal API Surface

Every API design MUST aim for a minimal API surface without sacrificing on product requirements. API design SHOULD NOT include unnecessary resources, relations, actions or data. API design SHOULD NOT add functionality until deemed necessary (YAGNI principle).

PreviousVersion Control SystemNextRules for Extending

Last updated