Install options
Every other way to install UI Craft — package managers, the Claude Code plugin, the Agent Skills CLI, git clone — plus where files land in each harness.
Updated 2026-07-25
Getting started gives you the one install that works everywhere. This page is for the cases it doesn’t cover: you already live inside a package manager, you only use Claude Code, or you want the skill vendored into a repo.
Every option below installs the same skill. They differ in how much of the system comes with it — the table at the bottom of each section says what you get and what you give up.
Package managers
Same ui-craft binary as the installer script, delivered by Homebrew or Scoop instead of curl.
macOS — Homebrew
brew install --cask educlopez/tap/ui-craft
ui-craft install
Windows — Scoop
scoop bucket add educlopez https://github.com/educlopez/scoop-bucket
scoop install educlopez/ui-craft
ui-craft install
You get the full system, same as the installer script. Pick this if you want brew upgrade to manage
the version.
Claude Code — native plugin
/plugin marketplace add educlopez/ui-craft
/plugin install ui-craft
Skill + all 25 slash commands + MCP gates in one step, wired the way Claude Code expects. Pick this if Claude Code is your only harness and you prefer staying in the agent.
Agent Skills CLI — skill only
npx skills add educlopez/ui-craft
This is the skill and nothing else. No slash commands, no review agents, no MCP quality gates, no hooks. You keep rung 0 and lose rungs 1–3. Use the installer script if you want the whole ladder.
Works with Codex, Cursor, Gemini, OpenCode, and Windsurf. The CLI detects the harness and drops the right mirror into the right folder — main skill plus the 3 style variants, materialized as peer skills (see Skill anatomy for what “commands” means outside Claude Code).
Using
npx skills add -gwith Claude Code? The skills CLI writes global skills to~/.agents/skills, but Claude Code reads~/.claude/skills(vercel-labs/skills#693). If the skill isn’t picked up, use the plugin install above, install per-project (drop-g), or symlink:ln -s ~/.agents/skills/ui-craft ~/.claude/skills/ui-craft.
Vendored — git clone or submodule
git clone https://github.com/educlopez/ui-craft.git ~/.skills/ui-craft
Or pinned into the repo, so every contributor gets the same revision:
git submodule add https://github.com/educlopez/ui-craft.git .skills/ui-craft
Pick this when you need the version pinned in git rather than installed per machine.
Where files land
| Agent | Folder | What lands there |
|---|---|---|
| Claude Code | .claude/ |
Main skill + slash commands (native) |
| Codex | .codex/skills/ |
Main skill + variants + commands-as-sub-skills |
| Cursor | .cursor/skills/ |
Same as Codex |
| Gemini | .gemini/skills/ |
Same as Codex |
| OpenCode | .opencode/skills/ |
Same as Codex |
| Generic agent-skills spec | .agents/skills/ |
Same as Codex |
Only Claude Code understands slash commands natively. Every other harness gets each command
materialized as its own peer skill, triggered by intent — “audit my UI”, “polish this page” — instead of
/ui-craft:audit.
Which install gives you which rung
| Install | Rung 0 · Ask | Rung 1 · Direct | Rung 2 · Persist | Rung 3 · Enforce |
|---|---|---|---|---|
| Installer script / Homebrew / Scoop | yes | yes | yes | yes |
| Claude Code plugin | yes | yes | yes | yes |
npx skills add |
yes | intent-triggered only | yes | no MCP gates or agents |
| git clone / submodule | yes | depends on your wiring | yes | wire it yourself |
Flags, subcommands, and the interactive hub are documented in the CLI reference.
Spotted something out of date? Open an issue on GitHub →