AI UX PlaygroundNewsletterJoin 2K+ AI designers and PMs on Substack. New teardowns, patterns, and prompts as they drop.

Prompt pack5 steps7 prompts

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.

  1. 01Lock taste and decisions

  2. 02Unslop the primary viewport

  3. 03Polish frontend UI

  4. 04Polish motion

  5. 05Persist in DESIGN.md

    Standing rules so the next agent session cannot reintroduce Inter, purple gradients, or bounce hovers.

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.