Claude Prompts for Design

Generate a structured interview script that pulls real brand attributes from a founder — past the rehearsed answers, into the specifics a designer can actually work from.

Produce a voice-and-tone document with a fixed voice, a tone spectrum across emotional contexts, and side-by-side examples that writers can copy from.

Produce a complete communications plan for deprecating a design system component — announcement message, migration guide, timeline, and the friendly-but-firm Slack templates that move teams off the old pattern.

Generate a complete component spec covering anatomy, states, behavior, accessibility, and tokens — the kind engineers actually want to read before implementing.

Generate a set of CTA variants for a specific moment in a product or marketing flow, each with a different psychological lever and a written rationale you can use to defend test picks.

Generate a tailored design review checklist that covers visual, interaction, accessibility, content, and edge-case considerations for a specific feature — not a generic template.

Generate a Request for Comments document proposing a substantive change to the design system — new component, breaking change, deprecation, naming convention — with the structure that gets actual decisions made.

Produce a charter that names every ritual on a design team — crit, review, all-hands, 1:1s — with cadence, attendees, format, and the specific outcome each ritual is supposed to produce.

Take a raw brand palette and produce a structured, layered token system (primitive → semantic → component) with names that survive a rebrand and scale across light/dark modes.

Write empty-state copy that does three jobs: explains what the surface will look like when populated, gives the user a single concrete next step, and matches brand voice without being cute.

Take a list of system error messages and rewrite each one to be plainspoken, blame-free, and actionable — with the structure: what happened, why, what to do next.

Apply Nielsen's 10 heuristics to a screen description or screenshot description and produce a prioritized issue list with severity ratings and concrete fixes.

Turn raw card-sort data (open or closed) into a prioritized set of information architecture recommendations with confidence levels and the trade-offs you're choosing between.

Generate an iconography style guide covering grid, weight, corner treatment, fill behavior, and how to evaluate whether a candidate icon belongs in the set.

Write the 'why' behind a screen layout — grid choices, hierarchy decisions, responsive behavior, and the trade-offs you considered — so engineers don't have to guess during build.

Generate the written rationale that accompanies a logo presentation — the story that explains the mark's construction, meaning, and behavior without resorting to brand-deck cliché.

Generate every line of copy in a multi-step onboarding — step titles, body, button labels, error states, success states — written as a coherent voice across the whole flow.

Define a responsive strategy that names breakpoints, explains why each exists, and specifies how core layout elements adapt — without spawning seven media queries per component.

Take raw usability test notes (your own or a researcher's) and turn them into a prioritized recommendation list ranked by impact, effort, and confidence — not a wall of observations.

Translate a user flow diagram or step list into a story stakeholders can read in 90 seconds — one that surfaces decision points, risks, and the user's emotional state at each step.

Generate a tight, bias-aware discussion guide for an unmoderated study (UserTesting, Maze, Lyssna) with screener questions, tasks, and follow-ups that work without a moderator in the room.

Take brand strategy inputs and produce three meaningfully different visual identity directions — each with personality, typography, color, and motion notes a designer could prototype against.