1Context

2Problem

3App

4Users

5Output

6Constraints

7Platform

8Prompt

Who are you, and what's your context?

A good prompt tells Lovable or Replit the environment it's building for. Help it understand who you are and what kind of organisation this is.

Your Role

e.g. Marketing Manager, Operations Lead, Founder

Industry / Type of Organisation

e.g. FMCG company, digital agency, healthcare provider, startup

Technical Environment

What tools does your team already use? What should the app integrate with (even loosely)?

What problem are you solving?

This goes directly into your prompt so the AI understands why the tool exists - not just what it should do.

Problem Statement

Paste from your canvas, or write it fresh. Be specific.

Who this affects

Who are the users of this tool? Who benefits when the problem is solved?

What are you building?

Give your tool a name and describe its core function in plain language.

Working Name

What would you call this tool? (Doesn't have to be final.)

What it does - core job

Describe the one primary thing this tool must do. If you had to pick one sentence.

Minimum Viable Version

What is the smallest version worth building first? Scope this down.

Who uses it, and what do they give it?

Define the user experience: who interacts with the tool, and what data or actions do they provide?

Primary User

Who is the main person using this tool day-to-day?

What the user inputs

What does the user give the tool? Text? Numbers? Uploads? Selections?

User's technical comfort level

What does it produce?

Describe what the tool outputs and how it should behave.

Output - what the tool produces

What does the user see or get at the end? Be specific about format.

Key behaviours / rules

What should the tool always do? What logic or rules should it follow?

What success looks like

How would a user know the output is correct and useful?

What must it NOT do?

Constraints are as important as requirements. They protect scope and prevent AI from over-building.

Out-of-scope features

What should NOT be built in this version? What is explicitly out of scope?

Risks to avoid

What could go wrong if the tool misbehaves? What safeguards matter?

Design constraints

Any specific design requirements? (Simple, mobile-friendly, specific language, etc.)

Where will you build it?

Choose the right tool for your use case.

Lovable

Best for tools with a visual UI - dashboards, forms, portals, anything a user interacts with visually. Generates full React apps. Fast prototyping, polished output.

Choose if your tool has screens and interactions.

Replit

Best for logic-heavy tools - data processors, calculators, scripts, utilities. More flexible, supports multiple languages, good for backend-first tools.

Choose if your tool primarily transforms or processes data.

Not sure? Describe your tool and we'll suggest one.

Or just pick one - you can always switch later.

Your Prompt

Here is your structured prompt. Copy it and paste it directly into Lovable or Replit. Then iterate from there.

Your prompt will appear here…

✦ Refine with Claude

Want Claude to review and improve this prompt before you paste it into Lovable/Replit? This uses the workshop server to send your prompt to Claude and get back a polished, more detailed version.