Think Before You Prompt

By the end of this lesson, you will be able to take any project idea — a data dashboard, a department website, an internal tool — and turn it into a specific prompt that can dramatically improve your first-draft quality. The secret is not better AI tools; it is better thinking before you type.

Mental model: the restaurant order

Think of prompting an AI tool the way you think about ordering at a restaurant. If you sit down and say “bring me food,” the kitchen has no idea what you want. You will get something, but probably not what you had in mind. However, if you say “I would like the grilled salmon, medium, with the roasted vegetables instead of fries, and the house vinaigrette on the side,” the kitchen knows exactly what to prepare.

AI tools follow your instructions as best they can, but they also infer missing details — so specificity reduces unwanted assumptions. Vague prompts produce vague results. Specific prompts produce specific results.

The most common mistake

Here is how most people use AI tools for the first time:

“Make me a website.”

The AI produces something. It is not what they wanted. They say “no, not like that” and get something else that is also wrong. After 20 minutes of back-and-forth, they are frustrated and the project is a mess.

The problem is not the AI. The problem is the prompt — and specifically, the thinking (or lack of it) that happened before the prompt.

The 60-second planning exercise

Before you open your CLI tool, spend 60 seconds answering these four questions:

1. What am I building?

Be specific. Not “a website” but “a portfolio site for a freelance photographer with a grid gallery, about page, and contact form.”

2. Who is it for?

This shapes everything. A tool for yourself can be rough. A tool for clients needs to be polished. A tool for beginners needs to be simple.

3. What does “done” look like?

Describe the end result. “When I open the page, I see a dark-themed grid of photos. Clicking a photo opens it full-screen. There is a navigation bar with three links. The contact form sends an email.”

4. What are the pieces?

Break it into parts. “I need: (1) a navigation bar, (2) a photo grid, (3) a lightbox for full-screen viewing, (4) an about page, (5) a contact form.”

Worked example: planning a real project

Let us walk through a complete example. Suppose you want to build an internal dashboard for your team that tracks project status.

Step 1 — What am I building? A project status dashboard that shows all active projects with their current phase, owner, and deadline.

Step 2 — Who is it for? My team of 8 people. They are not technical. It needs to be simple and visual.

Step 3 — What does “done” look like? When I open the page, I see a table of projects. Each row shows the project name, owner, status (a colored badge), and due date. There is a button to add new projects. Clicking a project opens its details.

Step 4 — What are the pieces?

1. A header with the team name
2. A table of projects
3. Status badges (On Track, At Risk, Blocked, Complete)
4. An “Add Project” form
5. A detail view for each project
6. Data saved to localStorage

Now combine that into a single prompt:

Create a project status dashboard for a small team.
- Header with "Operations Team Dashboard" title
- Main view: table of projects showing name, owner, status badge,
  and due date
- Status options: On Track (green), At Risk (yellow),
  Blocked (red), Complete (gray)
- "Add Project" button opens a form with fields for name, owner,
  status, due date, and notes
- Clicking a project row opens a detail panel with full info
  and an edit button
- Save all data to localStorage
- Dark theme, clean and minimal, easy to scan at a glance
- Mobile responsive

That prompt took about 90 seconds to write, and it is likely to produce a strong first draft. You may need one or two follow-up prompts to refine the details.

Why this works

Compare:

Vague prompt (bad):

Make me a website for my business.

Specific prompt (good):

Create a website for a dog walking business called "Happy Paws" with:
- Homepage: hero image area, three service cards (Daily Walks,
  Pet Sitting, Group Play), testimonials section, contact CTA
- About page: team bios with photos, company story
- Pricing page: three-tier pricing table
- Contact page: form with name, email, phone, message, service dropdown
- Dark green and cream color scheme
- Mobile responsive
- Professional but friendly tone

The second prompt will produce something 10x closer to what you want — and it only took an extra 60 seconds to think through.

The planning template

Here is a template you can copy and fill in every time:

I'm building: [type of project]
For: [audience]
It needs:
- [feature 1]
- [feature 2]
- [feature 3]
- [feature n]
Style: [visual description]
Tech preference: [framework/language or "your choice"]
When it's done, I should be able to: [describe the end result]

Example filled in:

I'm building: A recipe collection app
For: Myself (personal use)
It needs:
- Add recipes with title, ingredients, instructions, and photo URL
- Browse all recipes in a grid
- Search recipes by name or ingredient
- Tag recipes (dinner, dessert, quick, etc.)
- Filter by tag
- Save to localStorage
Style: Dark theme, warm colors (amber accents), food photography aesthetic
Tech preference: React with Vite
When it's done, I should be able to: Add my favorite recipes, find them
by searching or filtering tags, and see them in a nice visual grid.

Paste that directly into your AI CLI tool (such as Claude Code, Gemini CLI, or your preferred tool) and watch it work.

When planning is overkill

Not every task needs the full 60-second exercise. Simple, one-off changes like “rename the footer text” or “change the background color to #1a1a2e” can go straight to the AI without a plan. Use the planning exercise when you are:

• Starting a new project
• Adding a feature with multiple parts
• Working on something you have not built before

If the task fits in a single sentence, just prompt it. Save your planning energy for the work that benefits from it.

What a bad plan looks like

To see why planning matters, here is what happens without it:

“Build me an app for my team.”

The AI guesses. It builds a generic to-do list. You say “no, I meant a project tracker.” The AI starts over. You say “it needs status badges.” The AI adds them but puts them in the wrong place. Twenty minutes later, you have a mess of half-finished features and growing frustration. The problem was never the AI — it was the lack of a clear starting point.

The 80/20 of planning

You do not need to plan every detail. You need to plan the what and the why, not the how.

Plan these (what/why):

• What pages/sections does it have?
• What can the user do?
• What should it look like (general vibe)?
• What constraints matter?

Don’t plan these (how — let the AI decide):

• Which CSS properties to use
• How to structure the JavaScript
• What library handles the routing
• How state management should work

Your plan is the blueprint. The AI is the builder. A good blueprint does not specify what brand of nails to use — it specifies where the walls go and how many rooms to build.

Practice: plan before you prompt

Key takeaways

• 60 seconds of planning saves 20 minutes of frustration. Answer four questions before you prompt: What am I building? Who is it for? What does “done” look like? What are the pieces?
• Specific prompts produce specific results. Name features, describe layouts, specify colors and behaviors. The more detail you provide, the fewer assumptions the AI has to make.
• Plan the what, not the how. You are the architect, not the builder. Describe walls and rooms, not nails and lumber.
• Use the template. Copy the planning template, fill it in, and paste it as your first prompt. It works reliably and gives you a better starting point.
• Your domain knowledge is your superpower. You know what your field needs better than any engineer. That knowledge is what makes the prompt good.