pick-ui-library

Solid

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.

Web & Frontend 135 stars 6 forks Updated today NOASSERTION

Install

View on GitHub

Quality Score: 79/100

Stars 20%
71
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Picking The Right Library 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 | [...

Details

Author
arcboxlabs
Repository
arcboxlabs/linkcode
Created
2 months ago
Last Updated
today
Language
TypeScript
License
NOASSERTION

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Solid

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.

9 Updated 6 days ago
linkonai2026-kr
Web & Frontend Listed

choose-ui

Select and justify UI interaction patterns from user intent, real constraints, accessibility, and product context. Use proactively while planning, designing, implementing, or reviewing an end-to-end service, app, website, dashboard, admin, ecommerce, SaaS, or frontend—even when the user only asks to build the service and does not name components—whenever the work will introduce or choose interactive UI for input, selection, filtering, view switching, actions, navigation, or settings. Also use for explicit control comparisons and behavioral UX audits where replacement is allowed. Do not use for backend-only, API-only, or database-only work; visual-only styling or token changes; or implementation where the interaction pattern is already fixed and review is explicitly out of scope.

0 Updated 2 weeks ago
ProgWon
Web & Frontend Listed

ui-standout

Pick STANDOUT, fit-for-purpose UI components per use-case instead of reusing the same mundane flows. A 3-layer method: query real component catalogs (astryx / shadcn / Aceternity) for candidates, reject AI-slop defaults with a 46-rule taste gate (harvested from impeccable), and justify the pick with design principles (hierarchy, spacing, type, color, Von Restorff standout). Ships a use-case to component map so a checkout, dashboard, hero, onboarding or empty-state screen gets a standout component, not a stock grid. Use this BEFORE building, restyling, theming or polishing the rendered UI of a web, SSR or static app; when the user says a UI is bland/generic/mundane/"looks like every other app"; or when reviewing a built UI for slop. Not for backend/serverless-API/networking services (no UI), not for form validation/schema/handler code or tests that merely name a component, and not for charts specifically (the dataviz skill owns those).

1 Updated 3 weeks ago
M4NUSH7