25 Lovable Prompts You Can Copy and Paste

Help me define the smallest useful version of [idea] for [user].
Identify one core journey, essential screens, and what to leave out.
Discuss the options first; do not implement yet.

In Plan mode, turn this brief into a staged implementation plan: [brief].
Include dependencies, unclear decisions, and a concrete check for each stage.
Do not change the app until I approve the plan.

Review this feature request: [request].
Identify decisions that materially affect behaviour, permissions or cost.
Ask concise questions rather than guessing those requirements.

Draft concise project Knowledge from these confirmed requirements: [requirements].
Separate durable rules from temporary tasks and highlight contradictions.
Do not include secret values or invent business rules.

Break [feature] into small tasks in dependency order.
For each task, state its scope, what must stay unchanged, and how to test it.
Plan only; do not implement the whole feature at once.

Build the main screen for [user] to [action].
Use these real labels and content: [content].
Keep the first version focused on that action and include an empty state.

Improve the layout of [page] on narrow screens.
Keep the content, links and behaviour unchanged.
Check for clipped text, overlapping controls and horizontal scrolling.

Add a form for [purpose] with fields [fields] and required fields [list].
Validate inputs and show clear field errors, saving, success and failure states.
Do not report success if saving fails.

Add search by [fields] and filters for [criteria] to [list].
Show the result count and a useful no-results state.
Verify that combining filters returns the expected records.

Paginate [list] using the existing data-loading pattern.
Use [page size] records per page and preserve active search and filters.
Test first, middle, last and empty pages without missing or duplicate items.

On [page], change only [element] to match this reference: [reference].
Preserve navigation, data and all existing interactions.
Check the result at wide and narrow window sizes.

Review [screen] for keyboard access, input labels, focus visibility and contrast.
Fix the issues you find without changing the product workflow.
Verify that a keyboard user can complete [journey].

Make [record] persist using the project’s existing data service.
Show loading, empty and error states, and validate writes.
Verify by creating a record, refreshing, and reading the same record back.

Require sign-in for [private feature].
Enforce that users can access only their own [records], including direct requests.
Verify with two separate test accounts; do not rely only on hiding controls.

Add a password-recovery flow using the existing account system.
Include request, email-link return, expired-link and new-password states.
Do not expose whether an arbitrary email address has an account.

Add [admin action] for verified administrators only.
Check permissions where the action runs, not just in navigation.
Keep an audit record and verify a regular user cannot perform the action.

Connect [service] for [specific action] using its documented integration.
Request private credentials through the secure Secrets flow if needed.
Keep secrets out of browser code and logs; handle service failures clearly.

In Plan mode, outline checkout for [product and price].
Identify provider setup, plan requirements, payment verification and failure states.
Do not grant paid access based only on returning to a success page.

Prevent duplicate [form/action] submissions while a request is pending.
Preserve entered data on failure and allow a safe retry.
Verify rapid repeated clicks do not create duplicate records.

Bug: [observed result]. Expected: [expected result].
Steps: [exact steps]. It happens in [relevant state].
Investigate the cause before editing and fix only this issue.
Rerun the same steps to verify.

After this change, verify [new behaviour] and the existing flows [list].
Use realistic inputs and report what was tested and what remains unverified.
Do not claim success from compilation alone.

Test [feature] with empty, valid, invalid, duplicate and unusually long inputs.
Check loading and failure states as well as the successful path.
Fix only defects affecting this feature.

Investigate why [page/action] is slow using available measurements.
Identify the main bottleneck before changing anything.
Make a focused improvement and compare the same flow afterwards.

Review the release for broken navigation, data persistence, account permissions,
secret exposure, mobile usability and the main user journey.
List unresolved risks clearly; do not publish automatically.

Pause implementation. Summarise what has changed and what remains.
Return to the original scope: [scope].
Propose the smallest next step; do not add unrelated improvements.