Mini App Brief

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

What this is

The mini app brief is the first file the Blueprint Coach saves in localStorage App mode. It lives in your project folder as project-brief.md and keeps the app to one clear list of items.

Why it matters

The brief guides every build prompt without letting the AI invent extra scope. One saved brief keeps the whole build understandable across model switches, tutor handoffs, and new chat sessions.

What to do

Let the Blueprint Coach save the brief

In localStorage App mode, let the coach interview you one question at a time and save project-brief.md. Answer these to keep the app small:

1. What is the app called?
2. Who is the app for?
3. What is one item, and what 3-4 fields does it need?
4. What update action does an item have (mark done, change status, favourite)?
5. What theme do you want? Pick from a few beginner-safe options.
6. What would make this app too big for one session?

Keep it to one list of items

The brief must respect the Vibe 102 pattern:

one list of items -> add -> update or mark -> delete -> save with localStorage

No backend, login, database, charts, API, image upload, or multi-page routing.

Check the saved brief

Open project-brief.md and confirm it contains:

✓ app name
✓ user goal
✓ selected app type
✓ one item data shape (3-4 fields)
✓ max 3 core features
✓ initial design mood or DesignMD inspiration idea
✓ layout sections
✓ localStorage key name
✓ build order (small Work Cards)
✓ test checklist
✓ out-of-scope list

The final visual rules belong in design.md, not only in the brief. After the brief and data shape are clear, use the Design Direction phase to choose a DesignMD inspiration and save app-specific layout rules.

If a section is missing or the app has more than one list of items, ask the coach to fix it before you continue.

Do not paste private data, API keys, or passwords into any prompt. Use sample content when needed.

Common mistakes

• Starting code before the brief is clear.
• Accepting a brief with more than one list of items.
• Letting AI add filters, charts, accounts, or multiple pages.
• A design direction so vague that Tailwind polish becomes random.