Replace legacy outward contracts with a single canonical contract by removing compatibility logic.
npx skills add https://github.com/joshka0/foxctl --skill hard-cut-joshka0
Please help me install this Agent Skill. Skill: hard-cut Source: https://github.com/joshka0/foxctl/tree/main/configs/skills-pack/hard-cut Command: npx skills add https://github.com/joshka0/foxctl --skill hard-cut-joshka0
The hard-cut skill helps you intentionally remove legacy compatibility logic so your project uses one clean, canonical contract instead of carrying transitional shapes.
Use it when you want to refactor your system by replacing the legacy contract with a single canonical shape and explicitly removing compatibility behavior.
High-intent search queries and answers about installing and using this skill.
To remove legacy API compatibility logic, you replace transitional shapes with a canonical contract by eliminating fallbacks, shims, aliases, and dual-shape runtime behavior. This ensures all producers, consumers, and tests match only the new schema.
A hard cut for schema migrations is appropriate when backward compatibility is explicitly not desired. You apply it to intentionally break legacy outward contracts, removing transitional shapes and dual-runtime behavior to simplify the canonical schema.
The best way to break contract changes is replacing the legacy outward contract with a single canonical shape. This removes compatibility logic across routes, events, and configuration shapes while updating all docs and examples to match.
To update producers and consumers during legacy API deprecation, you enforce no fallbacks or legacy discriminator branches. All components, fixtures, and tests are updated to match only the new canonical contract.
Yes, you can break contracts for prompts, fixtures, and CLI commands. The approach applies to user-facing surfaces, removing compatibility logic and legacy branches to ensure they match only the canonical contract.
Limitations include enforcing no fallbacks, shims, aliases, or dual-shape runtime behavior. You must update all producers, consumers, docs, and examples simultaneously, as no backward compatibility is maintained during the legacy deprecation.
amorphous-dreamsDraft memetic surfaces from a lawful copy-shape while preserving the parent invariant.
velcraftingCoordinate API contract changes across teams to prevent drift.
jshsakuraDesign durable API contracts with endpoints, schemas, and versioning plans.
jonnymuirImplement alias shims and dual-contract validation for workflow JSON schema evolution.
