Principle Migrate Callers Then Delete Legacy Apis
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.
- Skill ID
- cursor/plugins/principle-migrate-callers-then-delete-legacy-apis
- Publisher
- cursor
- Repository
- plugins
- Installs
- 0
- Files
- 1
- Synced
- Sep 23, 2026
Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.
cursor/plugins/principle-migrate-callers-then-delete-legacy-apisInstalls these files- SKILL.md
What this skill tells the agent
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.
More from cursor
Use this skill in a project
Open any RiverX project, search the Skills panel for cursor/plugins/principle-migrate-callers-then-delete-legacy-apis, and install it in one click.