ask-emil

作者: emilkowalski

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

來自 emilkowalski 的更多技能

animate
emilkowalski
從零開始建立動畫,依序做出決定,以判斷整體是否自然流暢——是否該有動畫、目的為何、選用哪種工具、哪些屬性、哪條曲線與時長、如何打斷、如何結束。並撰寫實作內容。當被要求為某個東西加上動畫、增添動態感、讓元件更有生命力,或建立轉場效果時使用。若要評論現有動態效果,請使用 review-animations;若要審查整個程式碼庫,請使用 improve-animations。
animate-expo
emilkowalski
在 React Native 和 Expo 中製作動畫,依照決定動畫是否自然的順序做出選擇——是否要動畫、在哪個執行緒執行、使用哪些屬性、採用彈簧還是定時動畫、手勢如何交接,以及如何降級。使用 Reanimated、Gesture Handler、Expo Router 和 expo-haptics 撰寫實作。適用於在 Expo app 中製作任何動畫、加入手勢、底部面板、畫面轉場、按壓回饋或觸覺回饋,或修復裝置上卡頓的動態效果。適用於……
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
反向查詢詞彙表,將模糊描述的網頁動畫或動態效果轉換為精確術語(例如:「彈出視窗開啟時的彈跳效果」→ Pop in;「iOS橡皮筋滾動」→ Rubber-banding)。適用於使用者詢問「那個叫什麼…」或描述某個動態效果卻不知其名稱,並希望獲得正確詞彙以提示AI或設計師時使用。此功能僅用於命名效果,而非設計或實作。
researchdesigncreative
apple-design
emilkowalski
Apple 的介面設計與流暢、物理動態方法,專為網頁轉譯。適用於建構或審查手勢驅動的 UI、彈性動畫、拖曳/滑動/面板互動、動量與可中斷轉場、半透明材質與深度、字體排印(光學尺寸、字距、行距)、減少動態效果,或 Apple 風格介面背後的設計基礎(回饋、空間一致性、克制)。
ask-sonner
emilkowalski
Sonner(React toast 函式庫)使用指南——安裝並接上 Toaster、選用正確的 toast() 呼叫、promise 與 loading toast、更新、關閉及持久化 toast、樣式、主題與圖示、定位與多個 toaster。適用於使用 Sonner 或排解其問題時——例如 toast 未出現、出現兩次、失去樣式、忽略 Tailwind 類別、位於 modal 後方,或未跟隨深色模式。
break-ui
emilkowalski
透過輸入最糟情況的資料來嘗試破壞 UI 元件——長名稱、無法換行的電子郵件、單字母名稱、缺少欄位、超大數量、零個項目、長標籤、非拉丁文字、表情符號、極端數字——接著在「Demo data / Worst case」切換開關後方呈現,並回報所有出問題的地方及各自的修正方式。當使用者要求對元件或畫面進行壓力測試、找出問題或邊界情況,或「試試最糟情況」時使用。若要進行視覺設計評論,請使用 emil-design-eng;若要處理動態效果……
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