Teaching your AI agent to have taste in animations

What it does

This is a collection of agent skills — instruction packs for tools like Claude Code, Codex, and Cursor — focused on UI design and animation. Instead of letting your agent freestyle motion decisions, the skills encode rules from Emil Kowalski’s years at Vercel and Linear: which easing curve fits an enter animation, when a semi-transparent shadow beats a solid border, what not to animate at all. There are ~18 skills covering building, reviewing, auditing, choreographing, and even removing animations, plus adjacent concerns like gesture handling, mobile-native fixes, and stress-testing UIs with worst-case data.

The interesting bit

The premise is that agents don’t have taste, and taste is really a long list of small, specific mistakes to avoid — which is exactly the kind of thing you can write down. There’s even a remove-animations skill, a rare admission that most apps have too much motion, not too little.

Key highlights

• animate builds motion from scratch with correct curve, duration, and properties; animate-expo does the same for React Native, keeping motion off the JS thread
• review-animations and improve-animations audit existing code and produce prioritized, agent-executable plans
• break-ui stress-tests your interface with long names, empty lists, and huge counts
• apple-design distills WWDC design talks into web-applicable principles
• pick-ui-library stops agents from hand-rolling toast components or installing abandoned packages

Caveats

• The skills encode one person’s opinions and preferred libraries — that’s the point, but it means you’re buying into Kowalski’s taste, not a neutral standard
• Content is Markdown instruction files; the value depends entirely on your agent tool actually supporting skills

Verdict

Worth adding if you use an agent to build UI and are tired of ease-in enter animations and tooltips that fade in one at a time. If you hand-write all your motion yourself, this is someone else’s checklist, not yours.