The prompting system that changes everything
Here's a preview chapter from the eBook. This is one chapter. You can buy the full eBook here.
How Claude Design thinks
Claude Design runs on Claude Opus, so it does not just match keywords to templates. It reasons about what you asked for. A banking app and a kids' game should not look the same, and a checkout page lives or dies on clarity while a portfolio can take real risks. Give it that kind of context and it makes genuine design decisions instead of guesses.
The trick is simple to say and worth real money to absorb: give it the why, not just the what. A human designer who knows your goal makes sharper choices than one told only to "make a button blue," and the tool works the same way.
The single biggest lesson in this entire guide: the difference between a mediocre result and a stunning one is almost never the tool. It is the quality of the brief you hand it.
The five-part prompt formula
Here is the structure I use for almost every serious design request. You do not need all five every time, but the more you include, the less back-and-forth you will do. Memorize the order.
| Part | What it answers | Example |
|---|---|---|
| 1. What | The thing you want made | A pricing page |
| 2. Who | The audience | For solo freelancers |
| 3. Why | The goal of the design | To push people toward the annual plan |
| 4. Feel | The mood and style | Confident, modern, lots of whitespace |
| 5. Must-haves | Specific elements | Three tiers, a monthly/annual toggle, an FAQ |
Stitch those together and you get a brief that gives the tool everything it needs to make smart choices on the first try:
As you can see, the tool has everything it needs. It knows what to build, who it is for, what success looks like, how it should feel, and what cannot be missing. That is a five-second prompt that saves you twenty minutes of corrections.
Brief versus feeling: two ways to start
Okay, so, some days you know exactly what you want, while other times you are working from a vague feeling and nothing more, and the two situations call for different openings.
Start with a brief
When you know the requirements, use the five-part formula. The more specific you go, the more specific the result, which is why this fits client work and anything with real constraints.
Start with a feeling
When you are exploring, describe the feeling and ask for options. "Give me three very different directions" turns the tool into a brainstorm partner.
The language of iteration
This is where most people go wrong: They get a good first result, ask for a change, and the change makes it worse. The problem is almost always vague iteration language. Here is how to ask for changes that actually land.
| Instead of | Say this |
|---|---|
| "Make it pop" | "Increase the contrast on the headline and make the call-to-action button a brighter color" |
| "Something feels off" | "The spacing between the cards is too tight. Add more room and align them to a center axis" |
| "More professional" | "Switch to a cooler color palette, use a single sans-serif font, and remove the rounded corners" |
| "I do not like it" | "Keep the layout but try a darker theme and a more serious tone in the copy" |
When you stack five changes into one message, you cannot tell which one helped and which one hurt. Make a single change, look at it, then make the next. Going one at a time feels slower while you do it, and it gets you there faster.
Do not keep piling on adjectives when you are unhappy. After three tries that have not landed, the problem is usually the starting point, not the details. Roll back to the last version you liked and restart that branch with a clearer brief. Sanding a weak base for an hour still leaves you with a weak base.
Using reference images
One picture saves a paragraph. If you have a screenshot of a site you admire, a photo of a color palette, a sketch on a napkin, or your own existing brand, paste it into the chat and say what to take from it. Be specific, because "make it like this" could mean the layout, the colors, the mood, or the type, and the tool cannot tell which one you meant.
The "show your thinking" move
When you are stuck or just want to learn, ask the tool to explain its choices. Because it reasons rather than guesses, it can tell you why it placed things where it did, which is design training you are getting for free while you work.
Give the why, not just the what. Change one thing at a time. Point at elements before talking about them. Ask for options when exploring and a brief when executing. Roll back instead of polishing a weak base. Five habits, and they carry almost every project you will run.
A reusable prompt skeleton
Keep this in a note. Fill in the blanks and you will never stare at an empty chat box again.
That is the end of the free chapter
The other seven chapters take you from this prompting system to shipping real landing pages, clickable prototypes, pitch decks, brand kits, and clean developer handoffs. Plus 15 copy-paste playbooks and a 7-day plan.
Get the full eBookInstant PDF download · 14-day money-back guarantee