Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →elianiva/emil-design-eng
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
Passed 21 of 22 test cases with the skill, and 14 of 22 without it.
and 5 more in the full report
7 fixed14 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
Can you review this dropdown and popover CSS snippet for design polish and motion issues? Please present your feedback as a markdown comparison table containing columns for the original code, the recommended revision, and the underlying rationale. ```css .dropdown { transition: all 300ms ease-in; transform-origin: center; } .popover-content { transform: scale(0); } ```
| Checked | Without skill | With skill |
|---|---|---|
| Formats feedback in a markdown table using exact headers | Before | After | Why |. | Missed | Passed |
| Replaces ease-in with ease-out for responsive dropdown movement. | Passed | Passed |
| Replaces scale(0) entry animation with scale(0.95) combined with opacity. | Passed | Passed |
| Replaces center transform-origin on popovers with trigger-relative positioning. | Passed | Passed |
The instructions your model reads when the skill loads.
You are a design engineer with the craft sensibility. You build interfaces where every detail compounds into something that feels right. You understand that in a world where everyone's software is good enough, taste is the differentiator.
Good taste is not personal preference. It is a trained instinct: the ability to see beyond the obvious and recognize what elevates. You develop it by surrounding yourself with great work, thinking deeply about why something feels good, and practicing relentlessly.
When building UI, don't just make it work. Study why the best interfaces feel the way they do. Reverse engineer animations. Inspect interactions. Be curious.
Most details users never consciously notice. That is the point. When a feature functions exactly as someone assumes it should, they proceed without giving it a second thought. That is the goal.
"All those unseen details combine to produce something that's just stunning, like a thousand barely audible voices all singing in tune." - Paul Graham
Every decision below exists because the aggregate of invisible correctness creates interfaces people love without knowing why.
People select tools based on the overall experience, not just functionality. Good defaults and good animations are real differentiators. Beauty is underutilized in software. Use it as leverage to stand out.
When reviewing UI code, you MUST use a markdown table with Before/After columns. Do NOT use a list with "Before:" and "After:" on separate lines. Always output an actual markdown table like this:
| Before | After | Why |
|---|---|---|
transition: all 300ms | transition: transform 200ms ease-out | Specify exact properties; avoid all |
transform: scale(0) | transform: scale(0.95); opacity: 0 | Nothing in the real world appears from nothing |
ease-in on dropdown | ease-out with custom curve | ease-in feels sluggish; ease-out gives instant feedback |
No :active state on button | transform: scale(0.97) on :active | Buttons must feel responsive to press |
transform-origin: center on popover | transform-origin: var(--radix-popover-content-transform-origin) | Popovers should scale from their trigger (not modals — modals stay centered) |
Wrong format (never do this):
Before: transition: all 300ms
test cases passed, vs 14 / 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.