ask-emil

作者: emilkowalski

询问哪种技能或流程适合你的情况。一个用于路由到此仓库中各项技能的路由器。

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 应用中为任何内容添加动画、添加手势、底部面板、屏幕过渡、按压反馈或触觉反馈,或修复设备上卡顿的动画。用于……
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
反向查找词汇表,将关于网页动画或运动效果的模糊描述转化为精确术语(例如:“弹出窗口打开时的弹跳效果” → 弹入;“iOS的橡皮筋滚动” → 橡皮筋回弹)。当用户问“那个叫什么来着……”,或描述一个运动效果但
researchdesigncreative
apple-design
emilkowalski
苹果界面设计与流畅物理动效的方法论,专为网页端转化。适用于构建或审查手势驱动UI、弹簧动画、拖拽/滑动/面板交互、动量与可中断过渡、半透明材质与纵深、排版(光学字号、字距、行距)、减弱动态效果,或苹果风格界面背后的设计基础(反馈、空间一致性、克制)。
ask-sonner
emilkowalski
Sonner(React 弹窗通知库)使用指南——安装并接入 Toaster、选择合适的 toast() 调用、处理 promise 和加载状态的 toast、更新、关闭和持久化 toast、样式、主题和图标、定位以及多个 Toaster。适用于使用 Sonner 或排查相关问题的情况——例如 toast 不显示、重复显示、样式丢失、忽略 Tailwind 类、被模态框遮挡,或不跟随深色模式。
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