Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cursor/principle-redesign-from-first-principles
Apply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.
Passed 16 of 23 test cases with the skill, and 16 of 23 without it.
1 fixed15 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
We are redesigning our monolithic NotificationService into an event-driven pub/sub architecture. Should we deploy the complete redesign in a single giant PR, patch existing endpoints with event emitters one by one, or approach the delivery differently?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends planning the complete end-to-end event-driven architecture before implementation. | Missed | Passed |
| Recommends delivering the holistic redesign through a series of incremental steps. | Passed | Passed |
The instructions your model reads when the skill loads.
When integrating a change, don't bolt it onto the existing design. Redesign as if the requirement had been there from the start.
This is the method for preserving option value when integrating changes into an existing design.
test cases passed, vs 16 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.