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
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
웹 애니메이션이나 모션 효과에 대한 모호한 설명을 정확한 용어로 바꿔주는 역방향 검색 용어집입니다("팝오버가 열릴 때 통통 튀는 효과" → Pop in; "iOS 고무줄 스크롤" → Rubber-banding). 사용자가 "이런 걸 뭐라고 부르죠?"라고 묻거나, 모션 효과의 이름을 모르고 설명만 하면서 AI나 디자이너에게 지시할 정확한 단어를 원할 때 사용합니다. 효과의 이름을 찾는 용도이며, 설계나 구현을 위한 것이 아닙니다.
researchdesigncreative
apple-design
emilkowalski
Apple의 인터페이스 디자인과 유려하고 물리적인 모션 접근법을 웹에 맞게 변환했습니다. 제스처 기반 UI, 스프링 애니메이션, 드래그/스와이프/시트 상호작용, 관성 및 중단 가능한 전환, 반투명 소재와 깊이, 타이포그래피(광학적 크기 조정, 자간, 행간), 모션 감소, 또는 Apple 스타일 인터페이스의 기반이 되는 디자인 원칙(피드백, 공간적 일관성, 절제)을 구축하거나 검토할 때 사용하세요.
ask-sonner
emilkowalski
Sonner(React 토스트 라이브러리) 사용 가이드 — Toaster 설치 및 연결, 올바른 toast() 호출 선택, promise 및 로딩 토스트, 토스트 업데이트·해제·유지, 스타일링, 테마 및 아이콘, 위치 지정 및 다중 toaster 설정. Sonner로 작업하거나 문제를 해결할 때 사용 — 토스트가 표시되지 않거나, 두 번 표시되거나, 스타일이 사라지거나, 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