All guides

How to use Ideaunch

Turn a blueprint into a prompt pack for Lovable, Replit or Claude Code

How to go from a saved idea's blueprint to an ordered, copy-paste prompt sequence, and how to use it without wasting credits.

4 min readUpdated

A blueprint tells you what to build. A prompt pack tells your AI builder how, one step at a time and in an order that avoids rework. This guide shows you how to go from one to the other.

What's in a blueprint

When you analyse an idea and open its blueprint from My Ideas Vault, you'll see:

  • an overview of the product;
  • the page and screen structure;
  • copy: a headline and subheadline;
  • a flow diagram of how a user moves through it;
  • a suggested tools and stack;
  • estimated build cost, run cost and timeline.

Before you generate any prompts, spend two minutes editing the plan in your head. Cross out pages you don't need for version one. The fewer pages you start with, the fewer prompts you'll pay for.

Step 1: Open Prompt Pack and pick your builder

Go to Prompt Pack. First choose your builder: Lovable, Replit, Claude Code, Bolt, Emergent, Cursor or n8n. The prompts are written for the builder you pick, so choose the one you'll actually use.

Step 2: Start from your saved idea

Under Start from a saved idea, click your idea. Ideaunch fills in the idea and adds details from its blueprint: the page structure, the stack and the headline.

Now edit the Extra details box. This is where you make the pack yours:

  • remove pages you've decided to leave out of version one;
  • add anything the blueprint doesn't know, such as "payments through Stripe" or "must work well on mobile";
  • describe the look and feel in a few words, like "clean, dark, minimal."

Step 3: Generate and read the whole pack first

You'll get 10 to 15 prompts in order, usually starting with the data model, then sign-in, then the core screens, then polish. Each prompt has:

  • a title and a goal;
  • the prompt itself, ready to copy;
  • a verify step that tells you exactly what to click or check before moving on.

You'll also get a short summary and credit-saving tips for your builder. Read the whole pack once before you paste anything. If a prompt covers a feature you've decided to skip, leave it out now rather than undoing it later.

Step 4: One prompt, one check, then the next

The routine is simple:

  1. Copy prompt 1 and paste it into your builder.
  2. Wait for the builder to finish.
  3. Do the verify step. Actually click through it.
  4. If it passes, tick the prompt off in Ideaunch and move to the next one.

The ticks show your progress through the pack as you work. Every pack you generate is also saved, so you can reopen it later from your saved runs.

Step 5: When a step doesn't pass

Sooner or later, a verify step will fail. Don't paste "it doesn't work" into your builder. Instead:

  1. Re-read the prompt and check whether the builder skipped part of it. Sometimes the simplest fix is to paste the missing part again.
  2. If you have an actual error, open Fix-Loop Rescue. Choose the same builder, paste the error and describe what you were doing. You'll get a plain-English explanation and one focused fix prompt.
  3. Only move on once the step passes. Building on top of a broken step is how fix loops start.

Notes for specific builders

  • Lovable and Bolt: visual changes are cheap, structural changes are expensive. Get the data and sign-in right before you polish the design.
  • Replit: keep an eye on which files change. If a prompt touches files it shouldn't, say so in your next prompt.
  • Claude Code and Cursor: these work on a codebase you can see. Commit after each verified step so you can always roll back cleanly.
  • n8n: packs for automations are about nodes and data flow rather than pages. Test each node with real sample data before adding the next.

These are general habits, not rules. The tips in your pack are written for your builder and your project.

Keep the plan and the build in sync

Your Launch Plan has a Build stage with a task for getting your prompt pack. Tick it off once you've generated it, and use Roadmap if you'd like the blueprint turned into a wider step-by-step checklist beyond the prompts.

Don't have a blueprint yet?

You can still use Prompt Pack. Just describe what you're building in the box. But you'll get better prompts if you analyse the idea first. Start on the start page, then bring the result here.

Put this into practice

Describe your idea, or ask for one, and get a free analysis plus a five-stage launch plan in a few minutes.

Start free