VibeMap Logo

1.3 — Your first project

On this page

1.3 — Your first project

A project in VibeMap is one product you're building. Most people start with one project; you can have many.

Step 1 — Click "New Project"

From the dashboard, click New Project in the top-right.

📸 Placeholder: 04-new-project-button.png — dashboard with the New Project button highlighted.

Step 2 — Give it a name and a prompt

You'll see two fields:

  • Project name — e.g. "Coral Playground", "Mouthguard Builder". This is just a label; you can rename it later.
  • Project prompt — a one-to-three paragraph description of what you're building. This is the seed for everything VibeMap generates next.

The better your prompt, the better the spec. Two rules of thumb:

  1. Describe the product, not the implementation. "A scuba booking marketplace for the Red Sea, focused on first-time divers" is great. "A Next.js app with Supabase and Stripe" is not — VibeMap will pick the tech later if needed.
  2. Mention the user and the value. "Helps non-technical founders draft a spec their AI agent can build from" is much stronger than "An AI tool for specs."

📸 Placeholder: 05-new-project-form.png — the new-project form filled in.

Step 3 — Hit "Create"

VibeMap kicks off a multi-step generation pipeline. You'll watch it run in real time:

  • Summary — a tightened-up version of your prompt, with the product positioning extracted
  • Personas — the user types your product serves
  • Features — major capabilities, grouped logically
  • User stories — "As a … I want … so that …" statements for each feature
  • Acceptance criteria — the testable, claimable units of work your AI agent will pick up
  • Pages — the page-by-page UX outline
  • Schema — a database schema fit for the feature set
  • Files — a starter file/folder structure

This takes a few minutes. You can leave the tab — generation runs in the background and the progress strip persists across page loads.

📸 Placeholder: 06-generation-progress.png — the real-time progress strip with several phases complete.

Step 4 — Review what got generated

Every artifact is editable. Some sections (e.g. Features) are central — most of the downstream work depends on them — so the editor surfaces the Prepare → Review → Plan → Track flow that walks you through approving them in order.

  • Prepare — generate or regenerate any missing artifacts.
  • Review — read through what was generated. Edit anything that's off. Approve features and user stories you're happy with.
  • Plan — group your approved acceptance criteria into sprints (Pro+).
  • Track — the live kanban board your AI agent works against.

📸 Placeholder: 07-development-tab-strip.png — the Prepare/Review/Plan/Track strip with a progress indicator.

Step 5 — Connect your AI coding agent

When you're ready to start building, set up the VibeMap MCP server in your IDE. Then ask your agent: "What should I work on next?" — it'll claim a ready acceptance criterion and start.

Where to go next