This gives you the three main API versioning approaches with actual implementation code: URL path versioning (the recommended default), header-based, and query parameters. The version adapter pattern is handy for translating between formats, and there's a solid deprecation workflow with proper HTTP headers like Sunset and successor-version links. The best part is the practical guidance on what counts as a breaking change versus a safe one, plus a realistic 7-month deprecation timeline. If you're spinning up a new API or finally dealing with that v1 you've been maintaining for three years, this covers the decision points and gives you copy-paste starting code for Express routes.
npx skills add https://github.com/secondsky/claude-skills --skill api-versioning-strategy