正在加载视频...
视频加载失败
7 UI skills every design engineer should know when building with AI agents: 1. emil-design-eng 2. make-interfaces-feel-better 3. playwright-cli 4. react-doctor 5. fixing-accessibility 6. 12-principles-of-animation 7. shadcn
22 条评论

The best UI skill is still knowing what not to render. Every extra panel is a future support ticket wearing nice CSS.

playwright-cli in an agent loop is wild when it works still spend half my time watching it click the wrong aria-hidden modal though

Adding these to

fixing-accessibility is such an important skill for design engineers. can't overlook that!

Useful list. One thing I'd add: test on the phone you don't own Chrome was fine. A friends iPhone 12 ate the bottom of every weight field

Adding animation to the checklist, otherwise agents ship cardboard UI :)

The eighth skill is conflict resolution. Once two skills disagree on structure or styling, the agent needs an explicit priority order or it quietly invents one.

if designers overlook accessibility, they risk alienating a significant user base

react-doctor and fixing-accessibility are the two most people skip — and they're exactly what separates a demo from something you'd actually ship. Are these skills you feed the agent as context, or does it call them as tools at build time?

fixing-accessibility as its own separate skill instead of folding it into every other step is smart, most agents treat it as an afterthought bolted onto whatever they already built

Most designers overlook user feedback loops. Building AI agents requires constant iteration based on real user interactions , not just polished skills. That’s where true innovation in UI happens.

Agents don’t replace taste. They multiply whatever system you give them. Bad UI at 10x is still bad UI.

These skills are becoming table stakes for anyone building with AI.

Making interfaces feel smooth while keeping accessibility intact is crucial.

This is the right framing for vibe coding: the leverage is in the surrounding system, not just generating components. Which skill has paid off most in production—accessibility, browser testing, or a design system that keeps agent output coherent?

Design is changing 👀

Essential list, especially point #5. Accessibility often gets overlooked, yet it's foundational for inclusive AI experiences.

Wow, this is lovely.

didn't know existed, that's actually useful 👌

Bookmarked brother thanks for sharing

shadcn UI is a solid addition, the animation principles keep agents from feeling static

Chrome's own team packaging CWV skills into Claude. That's the shift. Domain expertise moving from docs to runtime.

