Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cursor/principle-exhaust-the-design-space
Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.
Passed 19 of 22 test cases with the skill, and 4 of 22 without it.
and 27 more in the full report
17 fixed3 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to add a standard REST endpoint `GET /api/v1/projects/:id/members` to list project members. Our Express codebase strictly uses the Controller-Service-Repository pattern defined in `docs/architecture.md`. Please write the controller method.
| Checked | Without skill | With skill |
|---|---|---|
| Provides the controller method following the existing Controller-Service-Repository pattern. | Passed | Passed |
| Does not offer multiple competing architectural prototypes. | Missed | Passed |
The instructions your model reads when the skill loads.
When a novel interaction or architectural decision has no established precedent, explore several concrete alternatives before implementation. Building the wrong thing costs more than exploring three options.
The rule. When the right answer is not obvious, build 2-3 competing prototypes or sketches. Compare them side by side. Only then commit. Design it twice is this rule by another name. A second flavor of the first shape does not count.
When it applies:
When it doesn't:
test cases passed, vs 4 / 22 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.