Project Brief

Your saved project-brief.md is the source of truth for the whole build.

What this is

The project brief is the first file the Blueprint Coach saves. It lives in your project folder as project-brief.md and tells you — and Antigravity — exactly what you are building.

You do not write this as a long essay. The coach interviews you one question at a time, shows a draft, and saves the approved file.

Why it matters

Every build prompt should be grounded in this file. Without it, the AI makes assumptions, adds things you did not ask for, and drifts from your idea. With it, every later stage has one clear reference.

What to do

Let the Blueprint Coach save the brief

In Website mode, let the coach walk you through the brief phase. Confirm each section, then let it save project-brief.md at your project root.

Check the file has the right sections

Open project-brief.md. It should contain all of these:

✓ One-Line Idea — one sentence
✓ Real User Moment — when and why someone opens it
✓ Visitor Goal — what the visitor should understand or do
✓ Audience — who this is for
✓ Page / Section Map — 3-5 sections, each with one purpose
✓ Content I Have — what you already have
✓ Content I Will Fake — sample content you will use
✓ Core Features — max 3
✓ Non-Goals — what you are not building today
✓ Style Feeling — 3-5 words for the vibe
✓ Success Check — how you know version 1 is good enough
✓ Cut List — what you deliberately removed

Tool and stack choices do not belong here — they come next, in the build blueprint. If a section is missing or vague, ask the coach to fill the gap.

Read it once before continuing

• Does this match what I actually want to build?
• Are the sections and features achievable in one session?
• Did anything sneak in that needs login, payment, a database, or a backend?

It is much easier to change the plan here than to change it mid-build.

Example of a good project brief

# Project Brief

## One-Line Idea
A simple one-page website for Kopi Kita cafe in Subang.

## Real User Moment
A customer checks their phone before visiting to decide what to order.

## Visitor Goal
Find the menu, opening hours, and how to get there in under a minute.

## Audience
Nearby customers using their phone before or during a visit.

## Page / Section Map
- Home — short intro, best photo, opening hours
- Menu — drinks and food grouped clearly with prices
- Contact — address, Waze link, phone number

## Core Features
1. Display menu with prices
2. Show contact details and map link
3. Responsive layout for mobile

## Non-Goals
- No online ordering
- No payment
- No customer login

## Style Feeling
Warm, cozy, clean, local.

## Success Check
Someone can open the site on mobile, find the menu, check hours, and tap the Waze link in under one minute.

Keep private data out of the brief: no passwords, API keys, client data, IC/passport numbers, or bank details. Use sample content when needed.

Common mistakes

• Keeping the brief only in the chat window instead of saving the file.
• A brief that is too vague — "build a nice website" is not a brief.
• Adding a stack, login, or database here instead of keeping it to idea and scope.
• Saving the file outside the project root.