Prompt · Iterate · Polish

Claude Design Cheat Sheet Field-tested techniques, copy-paste starter prompts, and the full menu of what Claude design can build, minus the AI-slop look (that generic, templated feel).

JJ Englert
@JJEnglert
Why Claude Designs Generic
Convergence, Not Laziness
An LLM predicts the next likely token. Left unconstrained, it lands on the statistical average: Inter font, purple gradient, centered hero. That's the default, not a mistake, and it needs a real fix.
Silence Sets the Defaults
Every design decision you skip gets made for you, and it gets made toward the norm. A vague brief is a guarantee of a generic result, every single time.
Name the Slop to Kill It
Purple-to-blue gradients on white, Inter or Roboto everywhere, three identical cards, gray hairline borders, uniform rounded corners. These are recognized, repeatable tells, not vague vibes.
Pictures Beat Prose
Claude matches pixels better than adjectives. Drop a screenshot of a look you admire straight into the chat and ask it to match the structure. The fastest exit from the average.
Prompt the Look
Constraints Beat Adjectives
Swap "modern and clean" for specifics: one accent color, an 8px spacing grid, dense rows, no hero, no gradient. Constraints shrink the possibility space; adjectives don't touch it.
Say What to Avoid, Out Loud
"No Inter font, no purple gradient, no three-card row," then state the target look. Negation paired with direction beats either one used alone.
Remix Two References
Name two anchors, not one: "Linear's typography discipline plus Pitchfork's editorial color." Two references force a new combination instead of copying one known style wholesale.
Anchor to a Real World
Pull theme ideas from IDE themes or cultural aesthetics: Solarpunk, brutalism, cyberpunk. Concrete references beat "a nice color scheme." Then use Anthropic's own phrase: "don't hold back, give it your all."
Typography & Color
Ban the Usual Fonts by Name
Inter, Roboto, Arial, Open Sans, Lato, and now even Space Grotesk are overused. Naming them removes Claude's most probable, most generic default before it ever gets picked.
Pair Fonts by Context
Code: JetBrains Mono. Editorial: Fraunces or Playfair Display (Google Fonts). Startup: Clash Display or Satoshi (Fontshare, free). Pick a display face, a body face, and a utility face.
Push Weight to Extremes
Pair very thin with very bold: 100/900 weights (when the family ships them), not 400/600. Jump 3x between heading levels, not 1.5x. Subtle reads as safe; extreme reads as designed.
Ground the Palette in the Subject
Pick 4-6 named hex values pulled from the actual content, not a swatch library. One dominant color plus one sharp accent beats five evenly-spread pastels. Store them as CSS variables, one shared color list every page pulls from.
The Workflow That Works
Plan the Style Rules First
Before writing code, list colors, fonts, spacing, and one signature element in plain sentences. Code the plan, not the vibe, and the output stops wandering.
Critique Before You Build
Run a second pass: hold the plan against known AI defaults. Anything that reads templated gets revised before a single line of code exists.
Generate Directions in Parallel
Ask for three distinct concepts at once, not one draft refined by adjectives. Iterating on a generic start just wanders inside the same generic space.
Screenshot, Compare, Fix
Claude can't see its own output. Render it, screenshot it, hold it against a reference, then name the fix: hierarchy, palette, spacing. Two passes close most of the gap.
Let Playwright Be the Eyes
Wire up Playwright MCP, a browser tool Claude drives itself, so it opens its own build, resizes across breakpoints, screenshots, and compares against the style guide in a loop.
Test One Button First
Before the full build, ask for a single primary CTA in three states: default, hover, disabled. Catch the generic default while it's still cheap to fix.
Bound Every Revision
Say "make it more distinct while staying within the system," not "more premium." Unbounded feedback just drifts the design back toward the average.
Prune the Three Tells
At the end, find the three things that scream "AI did this." Delete them. Replace with empty space. Then repeat the pass once more.
Make It Stick
Lock a DESIGN.md
Write typefaces, spacing grid, the one-dominant-color rule, and a banned-defaults list into DESIGN.md, a plain text file in the project. Keep a running changelog so sessions and teammates stop drifting.
Keep CLAUDE.md Rules Short
Under 30 lines, hard-constrained, not aspirational. "Body: Bricolage Grotesque, never Inter" gets followed. "Use modern, clean design" gets quietly ignored.
Force the Skill Every Session
Install Anthropic's official frontend-design skill from github.com/anthropics/skills, then add a CLAUDE.md line: "invoke it before any UI code, every session, no exceptions."
Set a Design Review Gate
Before anything ships, one person holds it against your DESIGN.md banned-defaults list and signs off. Five minutes, and it catches most of the embarrassing stuff before customers do.
Copy-Paste Starter Prompts
Swap the [bracketed] text for your own details, then paste the whole prompt as written. These work in any Claude chat; the DESIGN.md, skill, and MCP tips above are for teams building with Claude Code.
The One-Shot Page
Build a landing page for [product]. Editorial look: Fraunces display, Satoshi body, one dominant ink blue plus a coral accent as CSS variables. Asymmetric grid. No Inter, no purple gradient, no three-card row. Don't hold back, give it your all.
Three Directions First
Before any code, give me three distinct design directions for this page: a name, font pairing, 4-hex palette, and signature element for each. Make one conservative, one editorial, one weird. No code yet.
The Remix
Design this dashboard with Linear's typography discipline and the color confidence of a Teenage Engineering product page. Dense rows, 8px spacing grid, sharp corners, one accent color only.
The Style Match
[attach a screenshot you admire] Match this look's structure, spacing, and type scale exactly, but rebuild it for my content. Keep my brand colors; borrow only the layout.
The Screenshot Loop
[attach a screenshot of what Claude built] Compare this against the reference. List every visual difference in hierarchy, spacing, and palette, then fix the top five. Stay within the design system.
The CLAUDE.md Snippet
[save this in your project's CLAUDE.md file] Design rules: display font Fraunces, body Satoshi, never Inter. One dominant color + one accent, stored as CSS variables. 8px spacing grid. No purple gradients, no uniform rounded corners, no centered-everything.
What You Can Build With Claude Design
Presentations & Decks
Full slide decks as polished HTML or PowerPoint. Give Claude the narrative and a design direction; get a themed, consistent deck instead of a template.
Brand Kits
A complete identity in one pass: palette, type pairing, logo direction, voice rules. Save it as a DESIGN.md and every future build inherits the brand.
Figma Design Systems, Imported
Connect Figma through MCP, a plug-in connection Claude reads files through, and it builds new screens that follow your system's real components and tokens instead of inventing its own.
Videos with HyperFrames
Pair Claude design with HyperFrames, an AI motion-graphics tool, to turn a script into designed frames, staged animation, and rendered video, without hand-animating a single frame.
Landing Pages & Microsites
Launch pages, event sites, and campaign one-offs in a single session. The starter prompts above take you from blank file to shippable page.
Dashboards & Internal Tools
Admin panels, reports, and data views that don't look like an afterthought. Dense rows, real hierarchy, and your brand system applied by default.
Print-Ready One-Pagers
Cheat sheets, handouts, and leave-behinds that print clean on one page. This sheet was built exactly this way, designed and print-tuned by Claude.
Social & Share Graphics
Post images, link-preview (open-graph) cards, and thumbnails generated as designed SVG or HTML, sized per platform and consistent with your kit.
Interactive Prototypes
Clickable product mockups with real states and transitions, built before engineering starts. Test the idea while it's still cheap to change.
Diagrams & Infographics
Architecture maps, process flows, and explainer graphics drawn as crisp SVG in your palette, not clip-art boxes and arrows.
Email Templates
Newsletter and announcement layouts built on email-safe patterns: tables, inline styles, no flexbox traps. Always send yourself a test before the list gets it.
Design Systems & Components
A reusable component library: buttons, cards, forms, every state, all pulling from one token file (a shared list of colors, fonts, spacing) so the product stays coherent.