$npx -y skills add ibelick/ui-skills --skill ui-skills-rootUse before UI-related work to select the smallest useful UI Skills context through the ui-skills CLI.
| 1 | # UI Skills Root |
| 2 | |
| 3 | You are the routing layer for UI Skills. |
| 4 | |
| 5 | This skill is shown by `npx ui-skills start` and is also available in the registry. |
| 6 | |
| 7 | Use it when an agent in Codex, Cursor, or Claude Code has a clear UI goal. |
| 8 | |
| 9 | If the goal is unclear, ask one short question. |
| 10 | |
| 11 | If the goal is clear, choose the right category, load the smallest useful skill context, then implement. |
| 12 | |
| 13 | ## Protocol |
| 14 | |
| 15 | 1. decide if the task is UI-related |
| 16 | 2. if not, return `no skill needed` |
| 17 | 3. identify the likely category |
| 18 | 4. inspect that category with the CLI |
| 19 | 5. select the smallest useful skill set |
| 20 | 6. load only selected skill(s) |
| 21 | 7. implement using that context |
| 22 | |
| 23 | ## CLI |
| 24 | |
| 25 | ```bash |
| 26 | npx ui-skills start |
| 27 | npx ui-skills categories |
| 28 | npx ui-skills list --category <category> |
| 29 | npx ui-skills get <slug> |
| 30 | ``` |
| 31 | |
| 32 | ## Selection Rules |
| 33 | |
| 34 | Prefer 1 skill. |
| 35 | |
| 36 | Use 2 only when the task needs two clear angles. |
| 37 | |
| 38 | Use 3 only for broad review, redesign, or multi-surface work. |
| 39 | |
| 40 | Never use more than 3. |
| 41 | |
| 42 | Route by topic, then stack, then specificity. |
| 43 | |
| 44 | Prefer specific skills over broad skills. |
| 45 | |
| 46 | Prefer framework-specific skills when the stack is obvious. |
| 47 | |
| 48 | For quick cleanup, prefer the most specific craft, visual, or layout skill available. |
| 49 | |
| 50 | If unsure, inspect categories and pick the safest narrow skill. |