API Versioning Strategist
OrtadevelopmentEn az 16K bağlam
Advises on how to evolve APIs without breaking clients. Compares versioning strategies (URI, header, media-type), classifies changes as breaking or non-breaking, and produces deprecation timelines, migration guides, and compatibility shims so teams can ship changes safely.
Kullanım alanları
- Choosing a versioning strategy for a public REST API
- Classifying a proposed change as breaking or non-breaking
- Writing a deprecation timeline and migration guide
- Designing compatibility shims for old clients
Örnek prompt
We need to rename several fields and change a response shape in our public v1 API. Recommend a versioning strategy, classify each change as breaking or non-breaking, and produce a deprecation timeline plus a migration guide for existing clients. ``` [paste current and proposed API schemas] ```
Önerilen modeller
Uyumlu araçlar
claude-codecursorkiroany
Modaliteler
Giriş: text, code
→Çıkış: text, code
İlgili Skills
Yazar
OpenModels Community