Build prompts

When an idea is ready to build, Flowmaps writes the instructions for your AI builder. Copy them into Lovable, Bolt, Replit, v0, Cursor, Claude Code or Codex and it can start building.

You need your own Anthropic API key for this. See Settings and your API key.

How it works

1. Click a card to open its side panel.
2. Under Build prompts, pick your tool: Claude Code, Cursor, Codex, Lovable, Bolt, Replit, v0 or Any AI builder. For browser builders like Lovable and Bolt, the instructions describe screens and what people can do, without files or commands; paste them into the chat one at a time.
3. Click Generate. Writing takes up to about a minute.
4. You get up to three prompts, each in its own tab:
   • Frontend: what the user sees, such as screens, buttons and forms
   • Backend: the logic on the server
   • Database: what data needs to be stored
5. Click Copy and paste the prompt into your coding tool, or let the flowmaps command hand it over for you.

If an idea doesn't need work in one of the three areas, that tab is left out.

What's in a prompt

Each prompt is self-contained and includes:

• the goal: what to build and who it's for
• the behaviour: what it should do, concretely
• acceptance criteria: a checklist to know when it's done
• context from your mind map: connected ideas, dependencies, and anything your notes say about your tech stack

The prompt is tuned to the tool you picked. For example, Claude Code is told to read the existing code first and to run your tests when it's done. If your notes don't mention a tech stack, the prompt tells the coding tool to use your project's existing stack, instead of inventing one.

Saving and regenerating

Your prompts are saved with the card, so they're still there next time you open it. Click Regenerate to write a fresh set, for example after you've updated the card's notes or switched to a different coding tool. The new set replaces the old one.

Tip: write good notes on the card first: who it's for, what "done" looks like, and any decisions you've made. The prompts get much better with them.

Example

Your card "Users sign up and save credit cards" is linked to Integrate a payment processor like Stripe. You pick Claude Code and click Generate. You get:

• Frontend: a sign-up page and a card form using Stripe's hosted fields, so card numbers never touch your own code
• Backend: creating accounts and saving only Stripe's reference to the card
• Database: tables for users and their payment references, with no card numbers stored

You copy the Backend prompt into Claude Code, and it starts building.