/polish

Make it your own.

In Claude Code, use the slash command and add your context. In Codex, select polish from the just-vibe skill picker, then send the same brief.

Version 0.11.0 also supports /jv polish, /just-vibe polish and /jv:polish in Claude. See shortcut setup and context examples.

What the agent does

1. Capture baseline renders of the target viewport and state before editing, and prioritize the visible issues.
2. Fix the dominant hierarchy, spacing or alignment issue first, at the shared token or primitive when appropriate.
3. Compare the same viewport and state after the change.

Inputs

• existing UI, target screens, and desired refinements. Requires runnable UI or supplied render evidence.

Optional context: scope, references, constraints, successCriteria, environment, mode, budget.

Scope

Reads

Typography, spacing, hierarchy, consistency, and interaction detail; preserve product structure and behavior.

Writes

Apply: only the requested local changes and relevant isolated verification. Inspect/plan requests remain inspection/planning. External actions require their exact action and target in session authorization.

Mode

Apply; existing UI, target screens, and desired refinements. Requires runnable UI or supplied render evidence.

Prerequisites

Resolve the user brief and inspect the relevant project or supplied evidence. External capabilities are optional unless the selected action actually needs them.

Expected output

• Focused UI refinements with comparable before/after views and the behavior they preserve.

How the work is checked

• Refined alignment or hierarchy is visible; keyboard focus and responsive behavior are preserved.

When to stop or clarify

• Do not turn a polish task into a redesign. If rendering is unavailable, distinguish code changes from visually verified results.

Handling missing context

Infer

Resolve the named files, existing scripts, current task and earlier corrections from the conversation and repository.

Assume

Use the narrowest interpretation that completes a reversible local task; state a consequential assumption once.

Ask

Ask when competing targets or incompatible success conditions would change the result; continue independent inspection first.

Technical guidance

Evidence

Inspect rendered hierarchy, spacing, typography, alignment and interaction feedback in the existing design.

Method

Fix the largest visible inconsistencies while preserving established product behavior and visual intent.

Pitfall

Arbitrary token changes can improve one screen while breaking sibling components or dense content.

Check

Compare matched before/after states and inspect long text, narrow layout and focus/error treatments.

Situational decisions

When a visual change alters hit areas or focus visibility: Recheck interaction and keyboard behavior before accepting the visual improvement.

The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.

Keep exploring