ui-skills-root

ibelick/ui-skills · Agent Skill

Use when the user needs UI help and you must route by topic, stack, and intent to the smallest useful set of UI skills.

Overview

Publisher	ibelickCommunity
Repository	ibelick/ui-skills ↗
Skill folder	`ui-skills-root`
Stars	10,213
Forks	478
Bundled files	1
License	MIT
Last updated	October 25, 2026
Links	Skill source ↗ · Repository ↗

Mozgi check

What we found in the skill files. Details come with a subscription.

Security

medium risk · 1 point needs attention

Compatibility

instructions only — works with most agents

Similar skills

144 similar skills found

Also with subscription

Installation

A skill is a folder with a SKILL.md file. Pick your agent and run the commands in a terminal (macOS, Linux or Git Bash on Windows) from your project root.

Copy the prompt into Claude, Codex or another assistant: it will review the skill and install it for you.

Install the “ui-skills-root” skill from mozgi.io (https://mozgi.io/skills/ibelick-ui-skills-root/) for me.

1. Download the archive: https://mozgi.io/skills/ibelick-ui-skills-root/download
   If it fails, take the skill folder from the source: https://github.com/ibelick/ui-skills/tree/main/skills/ui-skills-root
2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me.
3. Put the “ui-skills-root” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.).
4. Make sure <skills folder>/ui-skills-root/SKILL.md exists.
5. Briefly tell me what this skill does and offer to try it on my task.

If you cannot do a step yourself, tell me what to click or type.

git clone --depth 1 --branch main https://github.com/ibelick/ui-skills.git /tmp/ui-skills
mkdir -p .claude/skills
cp -r /tmp/ui-skills/skills/ui-skills-root .claude/skills/ui-skills-root

Restart Claude Code — the skill appears in the list; call it manually with /ui-skills-root. For all projects use ~/.claude/skills.

git clone --depth 1 --branch main https://github.com/ibelick/ui-skills.git /tmp/ui-skills
mkdir -p .agents/skills
cp -r /tmp/ui-skills/skills/ui-skills-root .agents/skills/ui-skills-root

Codex looks for skills in .agents/skills from the current folder up to the repo root; call one with /skills or $ui-skills-root. For all projects use ~/.agents/skills.

git clone --depth 1 --branch main https://github.com/ibelick/ui-skills.git /tmp/ui-skills
mkdir -p .cursor/skills
cp -r /tmp/ui-skills/skills/ui-skills-root .cursor/skills/ui-skills-root

Cursor picks the skill up on start; call it with “/” in Agent chat. Cursor also reads .claude/skills and .agents/skills. For all projects use ~/.cursor/skills.

git clone --depth 1 --branch main https://github.com/ibelick/ui-skills.git /tmp/ui-skills
mkdir -p .gemini/skills
cp -r /tmp/ui-skills/skills/ui-skills-root .gemini/skills/ui-skills-root

Gemini CLI offers to activate the skill when a task matches — you approve it. For all projects use ~/.gemini/skills.

Review the source files

1 file Download Zip

Read SKILL.md and any companion files before deciding whether to install. Click a file to preview it.

SKILL.md contents

Original author text · read-only

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.

Frequently asked questions

What does the ui-skills-root skill do?

Use when the user needs UI help and you must route by topic, stack, and intent to the smallest useful set of UI skills.

How do I install ui-skills-root?

Open the “Installation” block on this page and pick your agent — Claude Code, Codex, Cursor or Gemini CLI — for ready-made commands that copy the skill folder to the right place. Or copy the prompt from the “Via assistant” tab and let the assistant review and install the skill.

Which AI models work with ui-skills-root?

Skills are plain Markdown instructions (the Agent Skills format), so ui-skills-root works with any agent that reads SKILL.md: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and more. The model loads the instructions only when a task matches the skill's description.

Is ui-skills-root free?

The skill is published openly by ibelick under the MIT license. The skill itself costs nothing — you only pay your AI provider for the tokens you use.

Is it safe to install skills?

A skill is a set of instructions your agent will follow, so read SKILL.md and its companion files before installing. Scripts in the skill folder only run if your agent runs them — keep an eye on what it does and do not grant unnecessary permissions.

How is a skill different from an MCP server or a plugin?

An MCP server or plugin gives the model new tools — code that runs and returns a result. A skill gives it knowledge and process: how to approach a task, which steps to follow and what good output looks like. It needs no server or API key.

Related skills

All skills →

agent-transcript Adds a redacted agent transcript to GitHub PR or issue bodies within OpenClaw agent-created workflows. openclaw389k

autoreview Automates code review using various AI models, providing structured reports and recommendations. openclaw389k

to-issues Breaks a plan or PRD into independently actionable issues. mattpocock304k

improve-codebase-architecture Scans a codebase for deepening opportunities and turns them into a prioritized visual report. mattpocock304k

triage Moves issues through a structured triage state machine. mattpocock304k

grill-with-docs Sharpens the domain model and updates supporting docs while grilling through design choices. mattpocock304k