Index of every page on this site: llms.txt
All skills
ibelick avatar

/ui-skills-root

@347d318 official
by Julien Thibeautibelick/ui-skills11k stars
542
Run it yourself

Use before UI-related work to select the smallest useful UI Skills context through the ui-skills CLI.

Use this Skill: https://skilld.dev/gh/ibelick/ui-skills/ui-skills-root

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈29 tokens for metadata: the name and description. ≈311 when used: this file.

Description uses 1.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈118 characters, or 1.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning5mo3 checks · Risk SAFE
  • Gen Agent Trust Hub5mo

    The skill facilitates the execution of a CLI tool to fetch and load external instructions into the agent's context. While this is the intended functionality, it creates a surface for indirect prompt injection from the remote skill registry.

  • Socket5mo

    1 alert: gptAnomaly

  • Snyk5mo

    Risk: LOW · No issues

Signed by skilld at 347d318. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 5 months ago
metadata
{
  "author": "ibelick",
  "version": "1.0.0"
}
  • CLI
  • ui
  • routing
  • skill-selection
  • design-systems
  • component-architecture

README badge

README badge for ibelick/ui-skills/ui-skills-root

This skill routes UI work by category through the ui-skills CLI, helping agents select and load only the narrowest relevant UI skill context before implementation. Use it when you need to pick between multiple UI skills or clarify an unclear UI task.

Generated from the current SKILL.md.

What does this skill do?
It's a routing layer that helps you select the right UI Skills to load based on your task. Run it first when you have a UI goal, and it guides you to the smallest useful skill context via the ui-skills CLI.
When should I use this skill?
Use it before starting UI-related work in Codex, Cursor, or Claude Code when you need help deciding which specific UI Skills to install.
Does this skill implement UI changes directly?
No. It identifies your UI task and routes you to other skills that do the actual implementation. This skill is the selection and routing layer only.
What if my task isn't clearly UI-related?
The skill will ask one short clarifying question to determine if UI work is actually needed, or return 'no skill needed' if it's out of scope.
Can I use more than one skill at a time?
Yes, but the skill recommends using only 1 skill for most tasks, up to 2 when two clear angles are needed, and 3 only for broad review or redesign work.

Generated from the current SKILL.md. These answers refresh after source changes.