ask-emil

Ask which skill or flow fits your situation. A router over the skills in this repo.

npx skills add https://github.com/emilkowalski/skills --skill ask-emil

Ask Emil

Before stating what a skill does or recommending one, read that skill's SKILL.md: the summaries here are for orientation only. Then recommend one skill (or one short sequence) for the user's situation, say why in a sentence, and name the skill they'd reach for next. Don't list the whole map back at them.

A flow is a path through the skills. Most UI work travels one main flow, from idea to shipped. Some skills are upkeep you run on a codebase that already exists, some are references that sit underneath everything, and a few stand alone.

The main flow: idea → ship

  1. Not sure what it should look or feel like? Detour through /prototype. It builds several genuinely different versions behind a live picker, then promotes the one you pick into the real code. Reach for it whenever a design question is hard to settle in words.

  2. Build it. Pick the builder by what's moving:

    • /pick-ui-library first if the task needs a dependency (dropdown, dialog, toast, drawer, command menu, drag and drop, charts). Don't let the agent hand-roll a toast.
    • /animate for one animation on the web: whether to animate at all, then tool, properties, curve, duration, interruption, exit.
    • /choreograph when several elements move together: staggers, hero entrances, view swaps, an item leaving while siblings close the gap.
    • /gestures when the user's finger drives it: drag, swipe, sheets, snap points, swipe-to-dismiss.
    • /animate-expo for any of the above in React Native or Expo.
    • /ask-sonner when the work is toasts with Sonner.
  3. Try to break it. Before calling it done:

    • /break-ui feeds it worst-case data (long names, empty lists, huge counts, emoji, non-Latin text) behind a toggle and reports what broke.
    • /review-animations reviews the motion in the diff against a strict bar. Default to flagging; approval is earned.
    • /mobile-native if it runs on a phone as a web app: sticky hover, the 100vh bug, inputs that zoom, safe areas.
    • /animation-performance if anything drops frames.
  4. Learn from the session. /learn-taste closes the loop. Run it at the end, in the same session, before you clear: it collects every design correction you made (including edits you made yourself) and turns each into a rule with its why, so the next agent doesn't repeat the mistake.

Upkeep: a codebase that already exists

Not feature work. Run these when you have a spare moment, or when the app "feels off".

  • The motion needs work across the app → /improve-animations. Read-only: it audits every animation and writes prioritized, self-contained plans another agent (or a cheaper model) can execute.
  • It feels static → /find-animation-opportunities. Read-only: it proposes motion with exact values, and rejects everything that shouldn't move. Build the ones you accept with /animate.
  • It feels slow or over-animated → /remove-animations. Edits code, but only to subtract: motion on keyboard actions, high-frequency surfaces, decoration with no purpose.

These three cover different questions. If the user isn't sure which, ask whether the problem is bad motion, missing motion, or too much motion.

References underneath

Model-invoked skills the others lean on. Reach for them directly when the knowledge, not a process, is what's missing.

  • /emil-design-eng: the core philosophy for UI polish, component interactions, and the invisible details. The fallback when no narrower skill fits.
  • /apple-design: Apple's principles for interface design and fluid, physical motion, translated for the web.
  • /animation-vocabulary: when the problem is the word. "What's it called when…" turns a vague description into the exact term to prompt with.

Standalone

  • /write-swift: modern Swift, Swift 6 concurrency, and native iOS code. Off the web flow entirely.

Common situations

You sayReach for
"Animate this"/animate
"These should come in one after another"/choreograph
"It doesn't follow my finger"/gestures
"It stutters" / "it's janky"/animation-performance
"Does this animation feel right?"/review-animations
"Make the app feel better"/improve-animations
"What could animate here?"/find-animation-opportunities
"Too much is moving"/remove-animations
"Give me a few options"/prototype
"Which library should I use?"/pick-ui-library
"Works in Chrome, feels wrong on my phone"/mobile-native
"Try the worst case"/break-ui
"What's that bouncy thing called?"/animation-vocabulary
"Stop making that mistake"/learn-taste

Lebih banyak skill dari emilkowalski

animate
emilkowalski
Membangun animasi dari awal, membuat keputusan dalam urutan yang menentukan apakah terasa benar — apakah sebaiknya dianimasikan sama sekali, untuk tujuan apa, alat apa, properti apa, kurva dan durasi apa, bagaimana cara menginterupsinya, bagaimana cara keluar. Menulis implementasinya. Gunakan saat diminta menganimasikan sesuatu, menambahkan gerakan, membuat komponen terasa hidup, atau membangun transisi. Untuk mengkritik gerakan yang ada, gunakan review-animations; untuk mengaudit seluruh codebase, gunakan improve-animations.
animate-expo
emilkowalski
Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and expo-haptics. Use when animating anything in an Expo app, adding gestures, sheets, screen transitions, press feedback or haptics, or fixing motion that stutters on device. For...
developmentdesign
animation-performance
emilkowalski
Keep web animations inside the frame budget — animate composite-only properties, keep motion off the main thread when the page is busy, and find the cause when an animation drops frames. Use when an animation is janky, choppy, stutters, or drops frames; when choosing which property to animate; when deciding between CSS and JS animation on performance grounds; or when reaching for `will-change` or GPU layers. For choosing easing, duration, or whether to animate at all use animate; for...
developmentdesign
animation-vocabulary
emilkowalski
Glosarium pencarian terbalik yang mengubah deskripsi samar dari animasi web atau efek gerak menjadi istilah yang tepat ("hal yang memantul saat popover terbuka" → Pop in; "gulungan karet iOS" → Rubber-banding). Gunakan saat pengguna bertanya "apa namanya ketika…", atau mendeskripsikan efek gerak tanpa mengetahui namanya dan ingin kata yang tepat untuk memicu AI atau desainer. Untuk memberi nama efek, bukan merancang atau membangunnya.
researchdesigncreative
apple-design
emilkowalski
Pendekatan Apple terhadap desain antarmuka dan gerakan fisik yang mengalir, diterjemahkan untuk web. Gunakan saat membangun atau meninjau UI berbasis gestur, animasi pegas, interaksi seret/geser/lembar, momentum dan transisi yang dapat diinterupsi, material tembus pandang dan kedalaman, tipografi (ukuran optik, pelacakan, leading), gerakan tereduksi, atau fondasi desain (umpan balik, konsistensi spasial, pengendalian diri) di balik antarmuka bergaya Apple.
ask-sonner
emilkowalski
Panduan untuk Sonner, pustaka toast React — instal dan hubungkan Toaster, pilih panggilan toast() yang tepat, promise dan loading toast, memperbarui, menutup, dan mempertahankan toast, styling, theming, dan ikon, penempatan dan banyak toaster. Gunakan saat bekerja dengan Sonner atau memecahkan masalahnya — toast yang tidak muncul, muncul dua kali, kehilangan gayanya, mengabaikan kelas Tailwind, berada di belakang modal, atau tidak mengikuti mode gelap.
break-ui
emilkowalski
Try to break a piece of UI by feeding it worst-case data — long names, unbreakable emails, one-letter names, missing fields, huge counts, zero items, long labels, non-Latin text, emoji, extreme numbers — then render it behind a "Demo data / Worst case" toggle and report everything that broke, with the fix for each. Use when the user asks to stress-test, break, or find edge cases in a component or screen, or to "try the worst case". For visual design critique use emil-design-eng; for motion...
testingdesigndevelopment
choreograph
emilkowalski
Coordinate several elements that animate together — decide what moves, in what order, how much they overlap, and what stays still — so a group reads as one intentional motion instead of a pile of separate animations. Use when building or fixing a staggered list, a hero entrance, a view swap inside a container, a multi-step flow, an element leaving while its siblings close the gap, a morph between rich states, or any interaction with several moving parts (icon + background + lines, panel +...
designdevelopment