You're building an API that needs to evolve without breaking existing clients. This walks you through URL versioning, header versioning, deprecation timelines, and backward compatibility patterns. The reference guides cover REST, GraphQL, and gRPC with real TypeScript and Python examples for version routing, adapter patterns, and testing strategies. The best practice list is solid: version from day one, support at least two versions simultaneously, give 6 to 12 months deprecation notice, and don't support more than three versions at once. It's comprehensive enough that you could hand this to a junior dev and trust they'll set up versioning correctly instead of painting themselves into a corner six months from now.
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill api-versioning-strategy