Dear Suzannah

Describe the data model and the user flow, not just the screens.

The real use case

You need a working full-stack web app — auth, a database, real pages — for an internal tool or a prototype. You’re not a full-stack developer, so the app has to come from a clear description and still hold up under real use.

The tool-specific prompt to use

This prompt is specific to Lovable and this use case. Paste it into the chat box, then replace the bracketed notes with your real project details.

Build a full-stack web app. App name: [name]. What it does, in one sentence: [e.g. 'lets our team log and track client onboarding tasks']. Data model (tables and fields): [list them, e.g. 'Client: name, status, owner_id; Task: title, due_date, client_id, done']. User roles and what each can do: [e.g. 'Admin: everything; Team member: own tasks only']. Pages I need: [list each, e.g. 'login, client list, client detail with tasks, add-task form']. Real validations: [e.g. 'due_date can't be past; task needs a title']. One full flow to make work end to end: [e.g. 'log in, open a client, add a task, mark it done']. Stack preference: [if any, else let Lovable pick]. Do not build pages I didn't list. Do not add fake data — use empty states. Give me the app, then list the 3 things I should test first. End with any data model choice I should confirm before I add real records.

Prompt length: about 200 words.

Make the result less generic

• Define the data model first — tables, fields, relationships.
• Name every user role and what it’s allowed to do.
• List each page and the action it performs.
• Specify the real validations on every input.
• Describe one end-to-end flow that has to work.

Quick human check

• Is the data model defined and sensible?
• Are auth and roles set up right?
• Are there validations on the inputs?
• Does one flow work end to end?
• Can it deploy, or is it just a preview?

Sources and further reading

• Lovable official source
• Lovable pricing or plans
• Lovable docs