samber/developer-platform-skills
api-versioning-policy
Define the versioning and deprecation policy for an API - version scheme choice (URI path, header, date-based account-pinned, or deliberate no-versioning), a written breaking-change definition, deprecation notice windows by audience, sunset communication (RFC 9745 Deprecation and RFC 8594 Sunset headers), enforcement at the sunset date (fall-forward vs hard cutoff), and breaking-change governance, with REST version-and-sunset and GraphQL continuous schema evolution treated as separate policies. Use whenever the user mentions API versioning, /v2, breaking changes, deprecation, sunset dates, or migration windows - even if they never say "versioning policy". Client SDK versioning is plain SemVer and belongs to samber/developer-platform-skills@sdk-portfolio-strategy.
Installation
npx skills add https://github.com/samber/developer-platform-skills
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Structures git workflow practices. Use when making any code change. Use when committing, branch…
830 installsAPI versioning strategies for ASP.NET Core. Covers Asp.Versioning library, URL segment, header,…
39 installsImplement semantic versioning (SemVer) with automated release management. Use conventional comm…
518 installsApply when installing, publishing, upgrading, or rolling back a VTEX IO storefront theme app (`…
510 installsAlso in this package
Other skills from samber/developer-platform-skills · top by installs.
npx skills add samber/developer-platform-skills
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.