L1Lesson 2Free

Answer Claude's clarifying questions

After this, you'll know that Claude usually asks a few questions before it builds, you'll understand why that makes the first build better, and you'll be able to answer those questions the way you'd brief a smart new colleague.

Before you start

Do Start a project and write a first prompt first; once you've sent that first description, this lesson covers the questions Claude usually asks right after, and how to answer them.

The idea

After your first prompt, Claude Design usually asks you a few quick questions before it builds anything. Answering them well is what makes the first build good.

A blank result card has three open decision sockets beside it, with the golden dot stuck before the next pass.

It might ask how long the page should be, what tone you want, or its aspect ratio (the page's shape: tall, wide, or square). A normal design app would never stop to ask. Claude does, on purpose.

Those questions are not the tool stalling or being slow. They are the tool refusing to guess. Every question Claude answers for itself is a chance to guess wrong, so when it asks instead, it is protecting your first build.

Think of it exactly like briefing a smart new colleague. A good new hire does not silently build the wrong thing.

They ask "how long should this run?" and "how formal should it sound?" first, because two minutes of questions saves a day of rework. Claude is doing the same.

Here is the before and after: One person treats the questions as an annoyance and types "whatever, just make it" to get past them. Claude has to fill the gaps with its own guesses, so the build comes back generic and off-tone.

Another person answers in a sentence or two, like a brief: "friendly but not childish, about one screen long." Their first build comes back specific and close, because Claude had real answers instead of guesses.

What Claude tends to ask about is the stuff that changes the whole design. It tends to ask about a few of these:

- What tone or feeling you want. - Roughly how long, or how many sections. - The aspect ratio: tall, wide, or square. - A company or product name to put on it.

The exact questions vary from project to project, so treat this as the pattern, not a fixed checklist. The move is always the same: answer plainly and specifically.

One worth knowing: if your first prompt was already very detailed, you may have little left to add when the questions come, so they go fast. That is a good sign, not a problem. It means your description in the last lesson did its job, and Claude had most of what it needed to start.

Treat Claude's questions as a free chance to aim the build. Answer them like a brief, and the first result comes back close.

Try it (8 min)

Watch out for

Rushing through the questions with 'whatever, just build it.' That hands Claude the guesses you were trying to avoid, and the first build comes back generic.
Answering with one word ('nice,' 'normal,' 'fine'). Vague answers help Claude as little as a vague prompt does; give it a full, specific sentence.
Assuming something is broken when there is little left to add and the questions go by fast. A very detailed first prompt covered most of it already, so a quick pass is a good sign, not an error.
Forgetting the questions are your chance to aim the build. Once it builds, fixing tone and length costs more builds than answering the question up front would have.

Paste this into Claude

I want to practice answering the kind of clarifying questions Claude Design asks before it builds, so I don't freeze or rush through them.

Pretend you are Claude Design and I've asked you to build [DESCRIBE YOUR PAGE, e.g. "a landing page (a single web page focused on one goal) for my freelance photography business"].

Please:
1. Ask me the 4 to 5 clarifying questions you'd most likely ask before building (about tone, length, aspect ratio, name, and anything else that would change the design).
2. After I answer, show me a "weak answer" and a "strong answer" for each question, so I can see what a brief-quality answer looks like.
3. Give me one simple rule of thumb for answering any setup question Claude asks, so I'm never stuck.

What a good response looks like

Here's your clarifying-questions practice, for the photography page:

**The questions I'd ask:**
1. What tone do you want (warm and personal, or sleek and high-end)?
2. Roughly how long (one screen, or a longer scroll with several sections)?
3. What aspect ratio or shape (one tall screen, a wide banner, a square)?
4. What name and tagline (the short line under a headline) should sit on the hero?
5. Do you have a color or font direction in mind?

**Weak vs strong answers:**
- Tone: weak "nice" → strong "warm and personal, like a friend with a camera, not corporate."
- Length: weak "normal" → strong "one screen, with a portfolio strip and a contact button."
- Aspect ratio: weak "whatever" → strong "one tall, single screen, sized for a phone."
- Name: weak "my business" → strong "'Field & Light Photography,' tagline 'Your day, honestly captured.'"

**Rule of thumb:** answer every question the way you'd brief a smart new colleague. One specific sentence beats a one-word shrug every time.

What good looks like

You can explain why Claude asks questions before building instead of just rendering right away
You can answer a question about tone, length, or aspect ratio in one specific sentence, like a brief
You understand that a very detailed first prompt leaves little to add, so the questions go fast, and that's a good sign
You treat the questions as a chance to aim the build, not as a delay to rush past

Design Question AimingMove through Answer Claude's clarifying questions, check proof, then fix only the weak part.

When this breaks

Breaks when you treat the questions as a delay to get past. They are the cheapest, fastest way to steer the first build, so skipping them just moves the work to expensive rebuilds later.
Breaks when your answers name nothing concrete. 'Make it good' tells Claude nothing it didn't already know, so it falls back on generic guesses for tone, audience, and length.

AI can help with this

Stuck on how to answer a setup question? Inside Claude Design, you can answer in plain words, even messy ones: 'honestly not sure, but it's for busy parents and should feel friendly.' Claude works with that and asks a sharper follow-up if it needs one. You don't have to get it perfect.

Three chosen answer tokens lock into the result card before it moves into the next design pass.

You can now

You can complete the lesson outcome in Claude Design or in the supporting tool the lesson names.

You can explain why Claude asks questions before building instead of just rendering right away.
You can answer a question about tone, length, or aspect ratio in one specific sentence, like a brief.
You understand that a very detailed first prompt leaves little to add, so the questions go fast, and that's a good sign.
You treat the questions as a chance to aim the build, not as a delay to rush past.

Key takeaways

Claude usually asks a few questions before it builds. They aren't a delay, they're a free chance to aim the first build, so answer them specifically, like briefing a smart new colleague.

Claude Design usually asks a few clarifying questions (tone, length, aspect ratio, name) before it builds.
The questions aren't the tool stalling; they're it refusing to guess, which protects your first build.
Answer like you'd brief a smart new colleague: one specific sentence, not a one-word shrug.
A very detailed first prompt leaves little to add, so the questions go fast when they come.
Two minutes of good answers saves the rebuilds a generic, guessed-at first build would cost you.

Go deeper

Was this helpful?

Up nextWireframe vs high-fidelity: when to use which

← Back to Claude Design

I want to practice answering the kind of clarifying questions Claude Design asks before it builds, so I don't freeze or rush through them. Pretend you are Claude Design and I've asked you to build [DESCRIBE YOUR PAGE, e.g. "a landing page (a single web page focused on one goal) for my freelance photography business"]. Please: 1. Ask me the 4 to 5 clarifying questions you'd most likely ask before building (about tone, length, aspect ratio, name, and anything else that would change the design). 2. After I answer, show me a "weak answer" and a "strong answer" for each question, so I can see what a brief-quality answer looks like. 3. Give me one simple rule of thumb for answering any setup question Claude asks, so I'm never stuck.

Here's your clarifying-questions practice, for the photography page: **The questions I'd ask:** 1. What tone do you want (warm and personal, or sleek and high-end)? 2. Roughly how long (one screen, or a longer scroll with several sections)? 3. What aspect ratio or shape (one tall screen, a wide banner, a square)? 4. What name and tagline (the short line under a headline) should sit on the hero? 5. Do you have a color or font direction in mind? **Weak vs strong answers:** - Tone: weak "nice" → strong "warm and personal, like a friend with a camera, not corporate." - Length: weak "normal" → strong "one screen, with a portfolio strip and a contact button." - Aspect ratio: weak "whatever" → strong "one tall, single screen, sized for a phone." - Name: weak "my business" → strong "'Field & Light Photography,' tagline 'Your day, honestly captured.'" **Rule of thumb:** answer every question the way you'd brief a smart new colleague. One specific sentence beats a one-word shrug every time.