Emil Kowalski turns UI guidance into skill

The real moat here is taste, not syntax: the file is useful because it turns design judgment into something agents can consume on demand.

• –The case-by-case recommendation is smart; always-on skills would likely flatten outputs and make everything feel the same.
• –Broad support across Claude Code, Codex, and Cursor keeps the barrier to adoption low.
• –It works best where heuristics are concrete, like animation timing, easing, performance, and UI polish.
• –It also acts as a distribution layer for Emil's course thinking, moving lessons from theory into actual implementation.
• –The risk is generic prompt drift if the skill reads like high-level advice instead of a sharp, opinionated checklist.