ux-component — Claude Code command: alias for /ux-design --component
ux-component — a slash command from the ux plugin that forwards the call to /ux-design --component to generate a single UI component. It is a temporary alias, removed in 4.1.
MIT ★ 110 updated 2026-11-02
/plugin marketplace add Laith0003/ux-skill
/plugin install ux@ux-skillWhat ux-component does
/ux-component does no work of its own. When invoked it tells the user the command has moved, then runs /ux-design --component with the same arguments — the component mode of the plugin's main command.
The frontmatter sets disable-model-invocation: true, so it only fires on an explicit user call. Tool access is limited to file reads and writes, ls, cat, find, mkdir, python3, Glob, Grep and Task.
The alias stays for compatibility until version 4.1, then it goes away. Scripts and habits should already point at /ux-design --component.
What it helps with
- generate a single UI component via the old command
- keep existing
/ux-componentinvocations working after the refactor - migrate to
/ux-design --componentwithout losing arguments
Example prompts for the agent
- /ux-component file upload button
- /ux-component product card for a catalog
How to install ux-component
1Plugin marketplace
/plugin marketplace add Laith0003/ux-skill/plugin install ux@ux-skill2Manually: put the files in place
.claude/commands/ux-component.mdCall it with /ux-component. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/ux-component.mdCall it with /prompts:ux-component. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/ux-component.prompt.mdManually: put the files in place
.gemini/commands/ux-component.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about ux-component
How do I install ux-component in Claude Code?
Add the marketplace with /plugin marketplace add Laith0003/ux-skill, then install the plugin with /plugin install ux@ux-skill. Alternatively place the file at .claude/commands/ux-component.md.
What does the ux-component command do?
It is an alias: it reports the move and runs /ux-design --component with the same arguments, generating a single component.
Why is /ux-component deprecated?
The command moved to /ux-design --component in version 4.0, and the alias is kept only until 4.1. Calling /ux-design --component directly is the durable option.
Source text
ux-component.md · MIT
--- description: Moved to /ux-design --component. Alias kept until 4.1. allowed-tools: Read, Write, Edit, Bash(ls:*), Bash(cat:*), Bash(find:*), Bash(mkdir:*), Bash(python3:*), Glob, Grep, Task disable-model-invocation: true --- # /ux-component (alias) `/ux-component` moved to `/ux-design --component` in 4.0: one component. This alias is removed in 4.1. 1. Tell the user in one line: "/ux-component is now /ux-design --component. Running it." 2. Run `/ux-design --component $ARGUMENTS`. Follow `commands/ux-design.md` in component mode, with the same arguments, exactly as if the user had typed the new command.
© Laith Aljunaidy · MIT · Laith0003/ux-skill