emilkowalski/skills

pick-ui-library

Pick the right library for a given frontend task from a curated, opinionated list — numbers, OTP inputs, charts, command menus, virtualization, drag and drop, toasts, state, styling, and more. Only runs when explicitly invoked; it does not trigger on its own.

165K installs 47K stars

Before you install

Last update
Files in folder
1
Scripts
No script files found
SKILL.md size
4.7 KB (about 1,198 tokens of context each time it loads)
License
MIT
Source on GitHub
emilkowalski/skills

Skills are plain text instructions the agent follows, sometimes with scripts. Check the source, prefer repositories with many installs and stars, and read any script it ships.

Install

npx skills add emilkowalski/skills@pick-ui-library

Runs in a terminal with Node.js 18 or newer. Add -y to skip the prompts and -g to install for every project instead of this one.

Install for your agent

npx skills add emilkowalski/skills@pick-ui-library --agent claude-code -y
Project install writes to
.claude/skills/pick-ui-library
Global install writes to
~/.claude/skills/pick-ui-library

Start a new session afterwards so the agent picks the skill up. In Claude Code you can also call it directly with /pick-ui-library.

What it does

Picking The Right Library 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…

Excerpt from the skill's own SKILL.md. Read the full file on GitHub before installing: skills run with your agent's permissions.

Categories

Related skills

  • emil-design-eng

    emilkowalski/skills

    This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

  • review-animations

    emilkowalski/skills

    Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.

  • apple-design

    emilkowalski/skills

    Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.

    219K installs 47KDesign & UIAnimation
  • animation-vocabulary

    emilkowalski/skills

    Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.

    217K installs 47KAnimationAI & agentsMobile
  • improve-animations

    emilkowalski/skills

    Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes rather than a review of a single diff.

  • find-animation-opportunities

    emilkowalski/skills

    Search a codebase or UI for places that don't animate but should, and reject everything that shouldn't. Read-only; it proposes motion with exact values, it does not implement it. Use when the user asks "what could be animated here?" or wants to "make this feel more alive". For fixing existing animations, use improve-animations or review-animations instead.

← Search skills

/skills/emilkowalski/skills/pick-ui-library/