Principle Migrate Callers Then Delete Legacy Apis

by cursorccb5507cec15No license10K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.

Instructions onlySoftware Development
AI-generated overview

Guides migrating internal API callers and deleting the legacy API in the same refactor wave.

What it does
This skill states a refactoring principle: when a new internal API is chosen, callers should be inventoried, migrated, and the old API deleted in the same wave rather than keeping compatibility layers. It also advises treating temporary adapters as exceptional and time-boxed, and updating tests to assert the new contract while removing tests tied to pre-refactor details. It produces guidance, not code or files.
When to use it
Use it when introducing a new internal API while old callers still exist and no external users depend on backward compatibility. It fits projects that can absorb coordinated breaking changes as part of a simplification or refactor initiative.
Requirements
None beyond the agent; instructions only, with no scripts or external tools.

Migrate Callers Then Delete Legacy APIs

When we decide a new API is the right design, migrate callers and remove the old API in the same refactor wave instead of preserving compatibility layers.

Rule:

  • Do not keep legacy API paths only because internal callers still exist
  • Inventory callers, migrate them, and delete the old API immediately
  • Treat temporary adapters as exceptional and time-boxed, not default architecture
  • Update tests to assert the new contract, and delete tests that only protect pre-refactor implementation details

When this applies:

  • No external users depend on backward compatibility
  • The project can absorb coordinated breaking changes
  • The new API is part of a simplification or refactor initiative

Keeping both old and new APIs creates dual-path complexity, slows cleanup, and makes the codebase feel append-only.

Source and attribution

Source:cursor/pluginsinpstack/skills/principle-migrate-callers-then-delete-legacy-apisat commitccb5507

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal