UI Skills: an interface-skill register for design engineers

Who it's for

Use UI Skills when you are a Design Engineer and need a set of interface skills an agent can use, not a prose design essay. The repository slogan is Skills for Design Engineers. More notes:

https://www.ui-skills.com/

Precondition: you can run npx on this machine. The first time, browse the register; do not get and write files at once. The notes name no specific clients; do not write one agent as official-only.

There is also an MCP channel that connects an agent to the register. That is a second path; do not bind it to the first CLI try, and do not get before skills have been shown.

First try in 3 minutes

Official page:

https://github.com/ibelick/ui-skills

Recommended start is read-only CLI commands. First see categories, then the example category motion (this does not take skill files):

npx ui-skills start
npx ui-skills categories
npx ui-skills list --category motion

start appears in the official command group; if it opens an interactive surface, only browse, do not pick an unconfirmed write. Use categories and list --category motion as observable success signals: you can see category names, and skill names under motion.

After you confirm you want a skill, the notes' example is:

npx ui-skills get baseline-ui

This fetches baseline-ui. Confirm the workspace may add files, then run, then open the new contents and check they match that skill. Do not invent other get names.

If the command fails, stop; do not switch to an installer that never appeared.

Use cases

Case 1: Browse with the CLI, then fetch one skill. Follow categories → list --category motion → after confirm, get baseline-ui. The check is: names come from the official CLI, and what you fetched is baseline-ui. The notes write no landing directory; do not invent a path.

Case 2: Connect the register via MCP. The notes say to connect the agent to

https://www.ui-skills.com/mcp

Available tools are list_skills and get_skill. First only run list_skills to see names, confirm, then get_skill. Visible text gives no client JSON or auth fields; if it will not connect, stop. There is also a distilled UI lesson at

https://www.ui-skills.com/playbook

That is reading material, not a third installer.

Boundaries

CLI is evidenced only as start, categories, list --category motion, get baseline-ui. Do not invent other subcommands or skill names.

MCP is evidenced only as the address above plus list_skills / get_skill. Do not add other tool names.

The notes give no language coverage, pricing, named clients, or landing directory. The Playbook is reading material only. Keep undocumented items unknown; do not invent installers or skill names.