ux-evolve — Claude Code command: what it does, how to install
The ux-evolve command for Claude Code is a legacy alias for /ux-polish --loop-only --rounds 5, running a file lint-fix-relint loop.
MIT ★ 110 updated 2026-11-02
/plugin marketplace add Laith0003/ux-skill
/plugin install ux@ux-skillWhat ux-evolve does
Calling /ux-evolve doesn't run its own logic. It prints one line about the move, then passes every argument straight to /ux-polish --loop-only --rounds 5, following the instructions in commands/ux-polish.md under loop-only mode with the old five-round cap. The new command reads --max-rounds as --rounds.
The loop keeps editing the file and rechecking it until the result clears the gate, and only then overwrites the original — after confirming the git tree is clean first. The alias itself is scheduled for removal in version 4.1, so scripts calling /ux-evolve by name will need to switch over.
What it helps with
- run a file through a bounded five-round lint-and-fix loop
- move scripts off the old command name onto /ux-polish without rewriting arguments
- swap in the fixed file automatically once it passes the check
- keep the git working tree clean before the final file replacement
Example prompts for the agent
- Run /ux-evolve on
Button.tsx - Loop /ux-evolve over the form component with the arguments you'd normally pass to ux-polish
How to install ux-evolve
1Plugin marketplace
/plugin marketplace add Laith0003/ux-skill/plugin install ux@ux-skill2Manually: put the files in place
.claude/commands/ux-evolve.mdCall it with /ux-evolve. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/ux-evolve.mdCall it with /prompts:ux-evolve. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/ux-evolve.prompt.mdManually: put the files in place
.gemini/commands/ux-evolve.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about ux-evolve
How do I install ux-evolve in Claude Code?
Add the marketplace with /plugin marketplace add Laith0003/ux-skill, then run /plugin install ux@ux-skill.
What does the ux-evolve command do?
It prints a one-line notice about the rename, then forwards its arguments to /ux-polish --loop-only --rounds 5, running the same lint-fix-relint loop capped at five rounds.
How is ux-evolve different from ux-polish?
It's only a forwarding alias: the actual logic lives in commands/ux-polish.md, and /ux-evolve just passes arguments through with the old five-round limit. The alias is set to be removed in version 4.1.
Source text
ux-evolve.md · MIT
--- description: Moved to /ux-polish --loop-only --rounds 5. Alias kept until 4.1. allowed-tools: Read, Write, Edit, Bash(ls:*), Bash(cat:*), Bash(grep:*), Bash(find:*), Bash(mkdir:*), Bash(date:*), Bash(git status:*), Bash(uxskill:*), Bash(python3:*), Glob, Grep, Task, WebFetch disable-model-invocation: true --- # /ux-evolve (alias) `/ux-evolve` moved to `/ux-polish --loop-only --rounds 5` in 4.0: the lint, fix, re-lint loop. `--max-rounds` is read as `--rounds`. As before, the loop replaces the original file when it clears the gate, now after a clean-tree check. This alias is removed in 4.1. 1. Tell the user in one line: "/ux-evolve is now /ux-polish --loop-only --rounds 5. Running it." 2. Run `/ux-polish --loop-only --rounds 5 $ARGUMENTS`. Follow `commands/ux-polish.md` in loop-only mode with the old five-round cap, with the same arguments, exactly as if the user had typed the new command.
© Laith Aljunaidy · MIT · Laith0003/ux-skill