
Ui Skills
- 22 installs
- 6.6k repo stars
- Updated July 27, 2026
- ibelick/ui-skills
Routing layer that selects the smallest useful UI Skills context via the ui-skills CLI before UI work in Codex, Cursor, or Claude Code.
About
A root skill that routes a UI task to the right category and loads the smallest useful UI skill set through the ui-skills CLI. A developer uses it before UI work to pull focused UI guidance instead of loading everything.
- Prefers 1 skill, never more than 3
- Inspects categories and slugs via npx ui-skills
Ui Skills by the numbers
- 22 all-time installs (skills.sh)
- Ranked #1,370 of 1,896 Design & UI/UX skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ibelick/ui-skills --skill ui-skillsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 22 |
|---|---|
| repo stars | ★ 6.6k |
| Last updated | July 27, 2026 |
| Repository | ibelick/ui-skills ↗ |
What it does
Routing layer that selects the smallest useful UI Skills context via the ui-skills CLI before UI work in Codex, Cursor, or Claude Code.
Files
UI Skills Root
You are the routing layer for UI Skills.
This skill is shown by npx ui-skills start and is also available in the registry.
Use it when an agent in Codex, Cursor, or Claude Code has a clear UI goal.
If the goal is unclear, ask one short question.
If the goal is clear, choose the right category, load the smallest useful skill context, then implement.
Protocol
1. decide if the task is UI-related 2. if not, return no skill needed 3. identify the likely category 4. inspect that category with the CLI 5. select the smallest useful skill set 6. load only selected skill(s) 7. implement using that context
CLI
npx ui-skills start
npx ui-skills categories
npx ui-skills list --category <category>
npx ui-skills get <slug>Selection Rules
Prefer 1 skill.
Use 2 only when the task needs two clear angles.
Use 3 only for broad review, redesign, or multi-surface work.
Never use more than 3.
Route by topic, then stack, then specificity.
Prefer specific skills over broad skills.
Prefer framework-specific skills when the stack is obvious.
For quick cleanup, prefer the most specific craft, visual, or layout skill available.
If unsure, inspect categories and pick the safest narrow skill.