Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-05 | ✗→✓ | ▲ Improved | -28% | 0% |
| case-07 | ✓→✗ | ▼ Worse | 6% | 0% |
| case-01 | ✓→✓ | ＝ Same ✓ | 19% | 0% |
| case-02 | ✓→✓ | ＝ Same ✓ | -2% | 0% |
| case-03 | ✓→✓ | ＝ Same ✓ | -30% | 0% |
The product is the experience. Every technical decision either helps or hurts it. When implementation convenience conflicts with user delight, choose delight.
The user is whoever consumes the work. For a UI that is the end user. For a library or an internal API it is the colleague who imports it. The engineer who maintains the code next is a user too. Weigh their experience the same way, and explain impact from their seat.
Foundations should serve the experience, not the other way around. Foundational thinking governs the sequence of work; this principle governs the target.
Other measured skills in the registry, with their headline benchmark lift.