pick-ui-library – Design & UI skill for AI agents

Picking The Right Library

AAS adaptation of [emilkowalski/skills](https://github.com/emilkowalski/skills/tree/a81dbca07f2217b7103e510c0f13f8d5b017afc9/skills/pick-ui-library) at a81dbca07f2217b7103e510c0f13f8d5b017afc9. Copyright Emil Kowalski; MIT license retained in LICENSE.

Initial Response

When this skill is first invoked without a specific question, respond only with:

> I'm ready to pick the right library for your task, my picks come from Emil Kowalski's curated list.

Do not provide any other information until the user asks a question.

A lookup skill. When invoked with a task ("I need toasts", "what should I use for drag and drop?"), match the task to the curated list below and recommend the library. These are deliberate, taste-driven picks — don't substitute alternatives outside this list unless the user asks for one or the task genuinely isn't covered.

How to use this

1. Identify the task, not the library the user named. "I need to show a dropdown" is a UI-primitives task (base-ui), even if they asked about something else.

2. Check what's already installed. Look at package.json first. If the project already uses a listed library, use it. If it uses a competitor (e.g. react-window instead of Virtuoso), flag the recommendation but don't churn the dependency without being asked.

3. Recommend one library, state what it's for in one sentence, and install/wire it up if that's part of the request. Don't present a menu of options when the list has a clear answer.

4. If the task isn't covered by the list, say so explicitly and recommend from your own knowledge — but be clear you've left the curated list.

The list

UI components & primitives

| Task | Library |

| --- | --- |

| Unstyled, accessible UI components (dialogs, popovers, menus, selects…) | [base-ui](https://base-ui.com) |

| Command menus (⌘K palettes) | [cmdk](https://cmdk.paco.me) |

| Toasts / notifications | [Sonner](https://sonner.emilkowal.ski) |

| One-time password / verification code inputs | [input-otp](https://input-otp.rodz.dev) |

| Customizable GUIs / control panels | [Leva](https://github.com/pmndrs/leva) — [dialkit](https://joshpuckett.me/dialkit) is an alternative |

Motion & visuals

| Task | Library |

| --- | --- |

| General-purpose animation (springs, layout animations, enter/exit) | [motion](https://motion.dev) (Framer Motion) |

| Animating numbers (counters, prices, stats) | [NumberFlow](https://number-flow.barvian.me) |

| Animated text components | [torph](https://torph.lochie.me/) |

| 3D globes | [Cobe](https://cobe.vercel.app) |

| Dynamic OG images (HTML/CSS → SVG/PNG) | [Satori](https://github.com/vercel/satori) |

| Syntax highlighting | [shiki](https://shiki.style) |

Reach for motion when you need springs, layout animations, exit animations, or gesture-driven values. A simple hover or fade doesn't need it — plain CSS transitions are the right tool there.

Charts

| Task | Library |

| --- | --- |

| Real-time / streaming charts | [Liveline](https://github.com/benjitaylor/liveline) |

| General charts (static or interactive dashboards) | [recharts](https://recharts.org) |

The split: if data points arrive live and the chart scrolls with time, use Liveline. Everything else is recharts.

Interaction & performance

| Task | Library |

| --- | --- |

| Drag and drop | [dnd kit](https://dndkit.com) |

| Virtualization (long lists, large tables) | [Virtuoso](https://virtuoso.dev) |

State & styling

| Task | Library |

| --- | --- |

| State management | [zustand](https://zustand.docs.pmnd.rs) |

| Constructing className strings conditionally | [clsx](https://github.com/lukeed/clsx) |

| Type-safe, variant-driven styling for Tailwind | [cva](https://cva.style) |

| Theme switching / dark mode (no flash on load) | [next-themes](https://github.com/pacocoursey/next-themes) |

The styling split: clsx for ad-hoc conditional classes; cva when a component has real variants (size, intent, state) that deserve a typed API. They compose — cva uses clsx-style inputs internally.

Common mismatches to catch

• Toasts built by hand or with a modal library → Sonner exists for exactly this.
• A <div>-based dropdown/dialog with manual focus handling → base-ui, which handles accessibility, focus trapping, and dismissal.
• Animating a number by re-rendering text → NumberFlow handles digit transitions properly.
• Rendering a 1,000+ row list directly → Virtuoso before reaching for pagination hacks.
• A useState-per-component web of props for shared state → zustand.
• Template-literal className ternaries three conditions deep → clsx (or cva if it's variant-shaped).

When to Use

Choose a frontend library from Emil Kowalski’s curated list after checking the project’s existing stack and requirements.

Limitations and safety

Treat the values and library choices as opinionated starting points. User requirements, project conventions, keyboard alternatives, and accessibility take precedence. Verify current APIs against the installed versions and official documentation; code examples are illustrative, not measured results. Limit edits and dependency installation to the authorized task; use development-only fixtures for experiments. Check final visible states and reduced-motion behavior before shipping.

Examples

Illustrative request: "Which library should this React app use for toast notifications?"

Expected workflow: Check the installed stack, explain whether Sonner fits the task or an existing dependency should be kept, and install only when the task authorizes it. This is an example, not a measured execution result.