Polish UI that doesn't look AI-made

Use this when a screen looks like generic AI output and you need a coding agent to lock taste, unslop, polish, and leave standing rules. Cursor, Claude Code, or Codex with the files open—not a chat-only redesign.

Use this

  • A landing page, dashboard, or component looks templated or AI-sloppy
  • You are polishing in Cursor, Claude Code, or Codex with repo context
  • You want motion craft after the static UI is intentional
  • You need DESIGN.md so the next agent session keeps the bar

Skip this

  • You need a full design system from tokens to rollout. Use the AI native design system pack
  • You only need a stakeholder critique meeting. Use the design critique pack
  • The problem is accessibility compliance first. Run an accessibility audit
  • You are writing brand strategy with no UI in the repo yet. Start with Build a brand kit, then return

Steps

Each step hands the next one a concrete artifact: direction → clean static UI → motion → DESIGN.md.

01Lock taste and decisions

04Polish motion

Frequently asked questions

Do I run every prompt every time?

No. If taste is already locked, skip to Unslop. If motion is the only problem, jump to Polish motion. If the UI is clean but agents keep inventing purple gradients, go straight to DESIGN.md.

ChatGPT or Claude instead of a coding agent?

Fine for Add taste or Grill while you are still briefing. For Unslop, Polish frontend UI, and motion, use Cursor, Claude Code, or Codex with the real files.

How is this different from the design system pack?

This pack fixes one screen’s craft and writes standing taste rules. The design system pack inventories tokens, components, docs, and rollout across the product.

Apple-style vs Polish UI motion?

Polish UI motion is the default craft pass (enter/exit, hover, restraint). Design Apple-style UI is for gesture physics: sheets, drag, rubber-banding, interruptible springs.