ui-picks

Selects and ports UI component libraries into projects by scenario.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/Suge8/skills --skill ui-picks-suge8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ui-picks
Source: https://github.com/Suge8/skills/tree/main/frontend/ui-picks
Command: npx skills add https://github.com/Suge8/skills --skill ui-picks-suge8

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing the right UI library for a specific interface scenario is time-consuming, and copying components into a project often leaves broken imports, mismatched design tokens, and leftover mock data. This Skill provides a curated routing table of UI libraries and a disciplined porting workflow so components land in the project correctly wired. ## Core Features & Use Cases - Scenario-based routing table: Maps interface needs (decorative effects, card layouts, state transitions, micro-interactions, product controls, marketing/dashboard blocks, AI chat UIs, UI sound effects) to a specific recommended library. - Porting workflow: A four-step process covering source extraction, dependency reconciliation, design-token mapping, and quality checks against AI-template artifacts, performance, and reduced-motion. - WebGL/shader reference: A dedicated reference for Canvas UI and Paper Shaders effects, enabled only when the user explicitly requests shader-based visuals. - Use Case: When asked to add a particle background or an AI chat interface, the Skill identifies the scenario, picks the matching library (e.g., assistant-ui for chat runtime), and ports the components with dependencies reconciled against the existing package.json. ## Quick Start Ask the agent to add a specific UI element to your project, such as "add a thinking-state loader and an AI chat interface to my React app", and it will select and wire the appropriate libraries.

Frequently Asked Questions about ui-picks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose a UI library for a specific interface scenario?▼

Identify the scenario from the task rather than library names the user mentions, then look up the routing table. For example, particle backgrounds map to effect libraries, AI chat runtimes map to assistant-ui, and icon morphing maps to morphicons.

How to port shadcn registry components into an existing project?▼

Copy the source into the project, strip mock data and site-specific CSS variables, then reconcile each dependency against package.json. Map colors, radius, fonts, and spacing to the project design system, choosing one token system rather than mixing both.

What UI library for AI chat interfaces in React?▼

Use assistant-ui for the chat runtime covering threads, streaming, and tool-call UI, installed via npx assistant-ui@latest init. For visual primitives like thinking states and approvals, use Beautiful UI or Fluid Functionalism components.

Does Appica UI work with React 18 or Tailwind v3?▼

No. Appica UI requires React 19 and Tailwind v4 as hard requirements and does not support downgraded adaptation. Its role-named tokens must also replace, not coexist with, existing shadcn tokens in the project.

When should WebGL shader effects be used in a web app?▼

Only when the user explicitly requests WebGL, shader, fluid, or glass effects. Canvas UI depends on the experimental html-in-canvas API in Chrome/Edge 140+, so fallback behavior and mobile power consumption must be tested before shipping.