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.

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."

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.

Step 4 — Review what got generated

Every artifact is editable, and each one has its own page in the project sidebar. Features are the load-bearing one — most downstream work depends on them — so start there, edit anything that's off, and approve the acceptance criteria you're happy with. Only approved ACs become claimable by an agent.

The three destinations that carry you from spec to build sit in the sidebar, in this order:

  • Prepare for Dev (Pro+) — enriches the spec into an atomic blueprint your agent reads. Optional, but it makes everything downstream richer.
  • Sprint Planning (Pro+) — groups your approved acceptance criteria into dependency-respecting sprints. Its own page, not a tab.
  • Development — labelled Hand off to IDE (or Sync with IDE on a code-first project). A single full-page kanban board with no tab strip; the ⓘ Handoff Instructions button at its top-right holds your MCP connection details.

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