Jakub KrehelHow I use AI as a design engineer on a daily basis.
Summary
A role built on craft has every reason to be sceptical of AI, and Jakub says so before explaining why he uses it daily anyway. Design engineering is largely trial and error, hours spent hunting the moment where something feels right, and AI makes throwing away a wrong concept cheap. The distinction he insists on is that it accelerates the work rather than replacing the thinking, and you have to understand what the agent is doing. Most of the value comes from setup. Short, specific project rules that reference other files, written once and reused everywhere.
View full writingGoes well with
emil-design-eng
The design-engineering house style behind Sonner and Vaul.
Emil's main skill. Mostly animation, with the UI-polish and component judgement that surrounds it: what to build, how far to push it, and when to stop.
npx skills add https://github.com/emilkowalski/skills
prototype
Builds several genuinely different UI variants behind a live picker.
Flip through real implementations instead of arguing about descriptions, then promote the one that wins.
npx skills add https://github.com/emilkowalski/skills --skill prototype
apple-design
Apple's interface and motion principles, translated for the web.
Distilled from the WWDC design talks. Gesture-driven UI, spring physics, interruptible transitions, translucent materials, optical sizing and the restraint underneath all of it.
npx skills add https://github.com/emilkowalski/skills --skill apple-design
Emil Kowalski