api-design

REST API design requires formal specifications that define endpoints, data contracts, and validation rules. This skill applies a Socratic workflow with decision matrices and checklists to produce consistent API specifications, whether designing new endpoints, standardizing existing patterns, or auditing architectures for coherence.

Standardizing REST APIs involves establishing splitting rules and applying gold-standard examples consistently. This skill uses a formal design workflow with instructional templates to identify inconsistencies, resolve pattern conflicts, and document decisions so all endpoints follow the same specification structure.

API auditing examines endpoints against specification criteria and consistency benchmarks. This skill provides a systematic review process with decision matrices and testing plans to surface design gaps, validate data contracts, and recommend fixes before deployment.

Formal API specifications must include explicit data contracts, validation rules, and endpoint definitions. This skill generates specification outputs with all required components, enabling teams to implement endpoints consistently and validate behavior against the documented contract.

Yes. This skill's Socratic workflow and templates apply to both new endpoint design and retroactive standardization. You can design incrementally by applying the formal specification process to each endpoint as it develops, ensuring consistency grows with your API.