Coding-agent skills

Updated: Sep 24, 2026

The UI Toolkit repository includes portable Agent Skills⁠ that help coding agents build Meta Ray-Ban Display applications with the toolkit. The skills provide focused guidance for:

choosing and composing toolkit components;
applying semantic tokens, materials, and motion;
structuring responsive screens;
preserving directional focus behavior; and
validating the finished application.

The skills are optional and are distributed through the UI Toolkit repository⁠, not through the npm packages. Install the toolkit from npm separately by following Installation.

Get the skills

Clone or download the UI Toolkit repository⁠, then run the installer from the repository root. Node.js 18 or later is required.

The installer copies the complete public skill set and verifies that every skill contains its required SKILL.md file.

Install for your account

An account installation makes the skills available across projects for the selected coding client.

Muse Code

node tools/install-skills.mjs --client muse-code --account

Codex

node tools/install-skills.mjs --client codex --account

Claude Code

node tools/install-skills.mjs --client claude-code --account

The destination depends on the client:

Client	Account destination
Muse Code	`~/.agents/skills`
Codex	`~/.codex/skills`
Claude Code	`~/.claude/skills`

Running the account command again updates toolkit-managed skills and removes managed skills that no longer ship. The installer preserves unrelated skills and same-named directories that it does not manage.

Use --force only when you intentionally want to replace a same-named skill directory that the installer does not currently manage:

node tools/install-skills.mjs --client muse-code --account --force

Install for one project

A project installation keeps the skills with one application. Pass the existing project directory:

node tools/install-skills.mjs \
  --client muse-code \
  --project /path/to/project

Muse Code and Codex project installations use .agents/skills. Claude Code uses .claude/skills.

Client	Project destination
Muse Code	`.agents/skills`
Codex	`.agents/skills`
Claude Code	`.claude/skills`

The installer refuses to overwrite an existing project skill directory. After updating the repository, use --force when you intentionally want to replace the previous project installation:

node tools/install-skills.mjs \
  --client muse-code \
  --project /path/to/project \
  --force

Do not install separate Muse Code and Codex copies into the same project because both clients use .agents/skills.

Use the skills

Start a coding task normally and describe what you want to build or change. The wearables-ui-toolkit-web skill is the entry point for toolkit work. It routes the task to the smallest relevant supporting skills, such as component usage, theming, materials, navigation, or validation guidance.

For best results:

Install the complete skill set rather than copying individual folders.
Start with a concrete task, such as building a settings screen or adding directional navigation to an existing route.
Ask the agent to use UI Toolkit for Meta Ray-Ban Display and preserve the toolkit’s component, token, and focus-navigation patterns.
Review the resulting application in desktop Chrome and on Meta Ray-Ban Display.

Example prompt:

Build a Meta Ray-Ban Display settings screen with UI Toolkit for Meta Ray-Ban
Display. Use semantic tokens, keep every action reachable through directional
navigation, and validate the finished screen.

Installer options

Option	Value	Purpose
`--client`	`muse-code`, `codex`, or `claude-code`	Selects the coding client and destination layout. Required.
`--account`	None	Installs into the current user’s client profile. Use exactly one of `--account` or `--project`.
`--project`	Existing directory	Installs into one project. Use exactly one of `--account` or `--project`.
`--force`	None	Replaces same-named skill directories at the destination.
`--source`	Skill directory	Installs from an alternate directory whose immediate subdirectories contain `SKILL.md` files.
`--prune`	None	With an account installation and alternate source, removes previously managed skills absent from that source.

The default bundled skill set is appropriate for normal use. --source and --prune are intended for advanced workflows that maintain an alternate skill collection.

Update or remove the skills

To update an account installation, update the repository and run the same account command again. To update a project installation, update the repository and rerun the project command with --force.

To remove a project installation, delete the toolkit skill directories from the project’s destination folder. For account installations, remove only the UI Toolkit skill directories and leave unrelated skills in place.