I made an interface cheat sheet full of small things you can do right away to make your interfaces better. It’s based on the /better collection of skills and it's a mix of best practices and some of my personal preferences. interfaces.dev/cheat-sheet↗
New skill: /find-animation-opportunities Search your UI for places that would genuinely benefit from motion, while also telling you what not to animate. github.com/emilkowalski/s…↗
Introducing Interfaces A design engineering magazine about building great interfaces. A new issue is released every month covering topics across animation, typography, layout, color and everything else that makes an interface feel great. interfaces.dev↗
When it comes to more visual work, like animations, coding agents don’t quite know what great feels like yet. Here’s my way of fixing it: emilkowal.ski/ui/agents-with…↗
Quick demo of the animations.dev skill file. Improve any animation based on my knowledge and experience gathered over the years:↗
Al produces motion that works, but feels mediocre, and if you can't tell the difference, you'll ship it. You'll settle for good enough, and that's not good enough. Train Your Judgement emilkowal.ski/ui/train-your-…↗
New lesson for upcoming animations.dev enrollment. It’s about training your judgement. You’ll see two versions of the same animation, your job is to choose one and explain why it’s better. A great skill to have when working with coding agents like Claude Code and Codex↗