---
name: ask-emil
description: Ask which skill or flow fits your situation. A router over the skills in this repo.
disable-model-invocation: true
title: ask-emil
canonical_url: https://skilld.dev/gh/emilkowalski/skills/ask-emil
last_updated: 2026-11-15T14:01:14.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install emilkowalski/skills/ask-emil`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/ask-emil`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/emilkowalski/skills/ask-emil) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/ask-emil`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/ask-emil --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/ask-emil --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 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 say | Reach 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` |
