Skip to main content

/

/

Stats

Actions

Tags

Stats

Actions

Tags

ClaudePluginHub

Community directory for discovering and installing Claude Code plugins.

Find plugins for your project

AI-powered recommendations based on your stack.

Product

Browse Plugins
Marketplaces
Pricing
About
Contact

Resources

Learning Center
Blog
Weekly Digest
Claude Code Docs
Plugin Guide
Plugin Reference
Plugin Marketplaces

Community

Browse on GitHub
Get Support

Legal

Terms of Service
Privacy Policy

Browse · Plugins · Top Plugins · Marketplaces · Components · Technologies · Skills · Agents · Commands · Hooks · MCP Servers · LSP Servers · Output Styles · Themes · Monitors

Categories · Productivity · Development · Testing · Deployment · Security · Documentation · Data · Utilities

© 2025 ClaudePluginHub

Community Maintained · Not affiliated with Anthropic

ClaudePluginHub

ClaudePluginHub

Tools Learn Pricing

Search everything...

api-versioning-strategy | api-development

Home
Skills
api-development
api-versioning-strategy

Skill

api-versioning-strategy

From api-development

Backward compatibility, deprecation policies, versioning schemes (URL, header, media type).

Popularity

Parent stars

13

Parent forks

2

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/api-development:api-versioning-strategy

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Managing API evolution without breaking clients.

SKILL.md

43 lines · ~370 tokens

Stats

Parent stars13

Parent forks2

MaintenanceFair

Last CommitMar 11, 2026

Actions

View Source View Plugin View on GitHub View README

Stats

Parent stars13

Parent forks2

MaintenanceFair

Last CommitMar 11, 2026

Actions

View Source View Plugin View on GitHub View README

API Versioning Strategy

Managing API evolution without breaking clients.

Context

You are planning API versioning. Minimize breaking changes; deprecate gracefully.

Domain Context

URL Versioning: /v1/users, /v2/users; easy to debug
Header Versioning: Accept: application/vnd.api+json;version=1; cleaner URLs
No Versioning: Add fields, never remove; extend don't replace
Deprecation: Announce, support for N months, then remove
Backward Compatibility: Old clients still work on new server

Instructions

Choose Strategy: URL, header, or additive only?
Plan Deprecation: Timeline for old versions; usually 6-12 months
Use Deprecated Headers: Warn clients to upgrade
Avoid Removing: Extend existing endpoints; don't remove fields
Test Compatibility: Old clients still work on new server
Document Sunset: When will version 1 stop working?

Anti-Patterns

Breaking clients without notice; bad reputation
Supporting too many versions; maintenance burden
No deprecation warnings; clients don't know to upgrade
Versioning when you could extend; simpler is better
API version unrelated to product version; confuses everyone

Further Reading

Semantic Versioning (semver.org)
API versioning approaches (Stripe, GitHub, Twitter examples)

$

npx claudepluginhub sethdford/claude-skills --plugin engineer-api-development

Similar Skills

api-versioning-strategy

149

Implements API versioning using URL paths, headers, or query parameters with deprecation timelines, backward compatibility, and migration strategies. Use for managing multiple versions or planning breaking changes.

api-versioning-strategy

View api-versioning-strategy

api-versioning

67

Guides API versioning strategies including URL path, header, query parameter, and content negotiation. Helps manage breaking changes, deprecations, and multiple versions.

3 tools

View api-versioning

versioning-and-evolution

12

Guides API versioning strategies: URL path vs headers, Stripe-style date-based, deprecation with sunset headers, backward compatibility, and non-breaking evolution.

api-design-principles

View versioning-and-evolution