api-design
Design and evolve API and module contracts with explicit behavior, validation, error semantics, authorization, and compatibility. Use for endpoints, schemas, service boundaries, SDKs, or shared interfaces. Follow existing protocol and repository conventions rather than imposing a new API style.
Pinned to revision 77677b5d0caa, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.