Prompts for Designers

A designer's week is a request with no problem behind it, a stakeholder who will only answer the questions you actually ask, six sets of interview notes and a readout on Thursday, a screen where the happy path is designed and nothing else has words, a decision you are about to lose the argument on, and a build that is not quite what you drew. This is a library of 24 prompts for that work: brief and framing, user research, UX writing, critique and justification, working with engineering, and portfolio and clients.

Each prompt tells the model what angle to take, what to work from, what structure to return and the one constraint that separates a professional answer from a generic one. They are built for the parts that actually go wrong: turning a vague request into a problem stated without naming the solution, interview questions about what people did rather than what they would prefer, synthesis that counts how many participants showed a pattern instead of promoting one vivid quote, microcopy for the empty and error states nobody designed, a self critique that names the single weakest thing, a handoff that specifies the paths users take by mistake, and an answer to the client who wants it to pop. Every prompt has a when to use line and a line on how to judge the answer, and the file ends with chains that run these prompts end to end.

One time purchase, yours forever, nothing to install. A single plain text file that works in Claude, Claude Code, ChatGPT, Gemini and Copilot. It produces thinking, structure and words rather than pixels, and the last prompt writes image generation prompts for building a moodboard.