pick-ui-library
SolidPick 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.
Install
Quality Score: 79/100
Skill Content
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
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.
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.
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).