Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
SkillScore92Maintained
Automatic
◆Design & UX Review pack
Last verified 10/10/2026
What it changes
Passed 22 of 24 test cases with the skill, and 18 of 24 without it.
Without skill75%
With skill92%
Checks it passed that the model alone missed
Require fixing alignment and transition details before release.
Recommend building a throwaway HTML prototype first to validate the interaction.
Prioritize CLI user experience over saving internal developer formatting effort.
and 1 more in the full report
4 fixed18 passed either way2 still failing0 broke
Pass-rate lift
+17 pp
Tokens
-3%
Agent turns
0%
Response time
-8%
Model gemini-3.6-flashMeasured 10/10/2026v122 of 24 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 4
Prompt
When planning the roadmap for a new dashboard application called MetricsPulse, the team is debating whether setting up the database schema and authentication infrastructure eliminates the need to focus on user experience design upfront. How do foundational technical setup decisions relate to the user experience goal?
What was checked, without and with the skill
Checked
Without skill
With skill
Explain that foundational infrastructure governs the sequence of execution while user experience remains the target.
Missed
Passed
Ensure technical foundations serve the target user experience.
Passed
Passed
case-09 · gemini-3.6-flash · 10/10/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md13 linessingle file
Experience First
When implementation convenience conflicts with user delight, choose delight.
Every feature, control, and option must be justified
Ship less, ship better (polished experience with three features beats rough one with ten)
Prototype before committing (design decisions are cheaper in throwaway HTML than production code)
Get the details right (transitions, alignment, spacing, feedback, error states)
Tighten the core loop (every feature should serve the central workflow or get out of the way)
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 perspective.
Foundations should serve the experience. Foundational thinking governs the sequence of work; this principle governs the target.