devrites-api-interface — contract before implementation
When a slice crosses a boundary (FE/BE, service/service, module/module) or exposes a public interface, define the contract first so both sides can proceed and the interface stays stable.
Define the contract first
- Shape — request/response or function signature; field names, types, optionality, units. Follow the project's existing naming and conventions.
- Status & errors — success codes, error codes, error body shape, vali
[Description truncada. Veja o README completo no GitHub.]