Menu
Ask Claude Code for frontend UI/design implementation, critique, visual hierarchy, responsive layout, or design polish.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Compatibility alias for stricter Claude review; prefer claude-review with --adversarial for new use.
Diagnose whether Claude Code is installed and authenticated for this local Codex plugin without making a billable Claude call.
Run a structured, read-only Claude Code review over the current git diff or a branch diff.
Delegate a foreground read-only or write-capable task to Claude Code from Codex using the local companion script.
Configure or explain the optional Codex Stop hook that can run a read-only Claude review when a turn ends.
Cancel a running Claude Code companion job by sending process signals through the plugin job index.
| name | claude-ui |
| description | Ask Claude Code for frontend UI/design implementation, critique, visual hierarchy, responsive layout, or design polish. |
Use this skill when the user wants Claude Code's help building or polishing frontend UI, landing pages, product flows, responsive layout, accessibility, or visual design details.
Use the companion script from the installed plugin root. If the current working
directory is not this plugin checkout, resolve the script relative to this skill
file, for example ../../scripts/claude-companion.mjs, and pass --cwd <target-repo> for the repository being edited or critiqued.
Real UI/design calls can send prompts and workspace context to Claude Code and may spend quota. If the Codex host offers persistent approvals, ask the user to approve the narrow prefixes node scripts/claude-companion.mjs ui and node scripts/claude-companion.mjs design instead of broad commands like node. If host policy blocks external disclosure, do not bypass it.
If the host approval system denies the UI/design command because it would disclose workspace context to Claude, stop and report that Claude UI/design was blocked. Do not silently complete the task locally with Codex during a Claude integration smoke test. Only fall back to local Codex implementation if the user explicitly asks for a local fallback after the block is reported.
Run a write-capable UI/design task:
node scripts/claude-companion.mjs ui --prompt "<ui or design request>"
Run a read-only UI critique:
node scripts/claude-companion.mjs ui --prompt "<ui or design request>" --plan
The design subcommand is an alias:
node scripts/claude-companion.mjs design --prompt "<ui or design request>"
Behavior:
acceptEdits by default because UI polish often needs file edits.plan permission mode when --plan is supplied.--cwd, --model, --effort, --background, --wait, --resume, --fresh, and --state-dir.--trust-local-dev in trusted local frontend projects when Claude should be allowed to edit files and run common local test commands without a nested Claude approval stop.--allow-tool <pattern> or --allowed-tools-file <path> for narrower approved Claude Code tool patterns.--model opus for serious design decisions when the user approves cost and quota impact.--effort low for cheap smoke checks.If Claude Code requests tool approval during noninteractive UI work, the plugin reports permission_blocked. Surface the blocked tool and suggest --trust-local-dev only for trusted local repositories, or a narrower --allow-tool pattern.
Host/Codex approval and Claude Code tool approval are separate layers. Host denial happens before Claude runs; permission_blocked happens after Claude starts and requests its own tool approval.