A prompt is a written request
You do not need a special coding language. A useful prompt says what to change, where to change it, what the result should be, and what to preserve. Describe the visitor's task in plain words. Give real wording when exact copy matters. If you do not know a term, describe what you can point at: 'the menu at the top' is enough.
Before and after: the first request
Before: 'Make me a nice cleaning website.' The builder has to guess the pages, purpose, and business details. After: 'Build an unpublished practice cleaning-service website with Home, Services, About, and Contact pages. The main action is Request a Quote. Use sample wording labeled as practice. Leave out accounts, booking, and payments. Make text readable on a phone. Do not invent testimonials or a phone number.' The second request gives a clear boundary and a way to judge the result.
Before and after: a revision
Before: 'Fix the whole thing and make it better.' That can change parts you already liked. After: 'On Services only, shorten each description to two sentences and make the Request a Quote link easy to find. Keep the service names, menu, colors, other pages, and contact destination unchanged.' Small requests are easier to check and easier to undo if the result is wrong.
Ask for a plan when you are unsure
Use the planning or discussion option available in your workspace to ask questions before changes, or plainly say 'Explain the options first; do not edit yet.' Ask what a feature needs and which services may charge for it. For example, 'What would a working quote form need, where would replies go, and what would stop visitors from seeing each other's entries?' Read the answer and confirm the intended next step rather than accepting every suggested feature.
Refine from what you can observe
After each request, open the changed page and do the visitor's task. Tell the builder the difference between what you expected and what happened. Screenshots can clarify a layout problem, but remove personal information first. If a change fails twice, stop repeating 'fix it.' Describe one reproducible problem, ask for its cause, and consider restoring the last working version.
Keep private details out of prompts
Do not paste passwords, secret keys, customer addresses, bank details, or private messages into a building chat. A secret key is a private credential that lets software use a service. Use the service's approved secret-setting controls, not public page text or browser code. Use pretend records for practice. Ask for a privacy review before connecting real data; the prompt alone is not a security guarantee.
Example prompts to copy and adapt
Replace [BRACKETS] with approved details. Use pretend information for practice, never passwords or customer records.
Fill-in change request
On [PAGE], change [ONE THING] so visitors can [GOAL]. Use this approved wording: [TEXT]. Preserve [PARTS TO KEEP]. Do not add [EXCLUDED FEATURES]. Check [OBSERVABLE RESULT] after the change.
Ask before changing
I am considering [FEATURE]. Explain what it needs, where any information would be stored, likely cost types, and the simplest alternative. Do not edit the project or connect a service yet.
Report a problem
On [PAGE] using [PHONE/COMPUTER AND BROWSER], I [EXACT STEPS]. I expected [RESULT], but [ACTUAL RESULT] happened. Investigate this problem only. Preserve other working features. Explain the cause and how I can verify the fix.
A real-world example
In the practice cleaning site, the Services page is too wordy. Ask for two-sentence descriptions on that page, not a complete redesign. Read the result aloud, check the quote link, and confirm the other pages stayed the same.
Steps to take
- Rewrite one vague request using page, action, result, and boundaries.
- Use one revision prompt on the practice site.
- Compare the changed page with your expectation.
- Exercise: write a troubleshooting prompt without any private data.
Prompt check
This checklist is optional and not saved. Copy it to keep a personal note. Do not enter sensitive information.
Go deeper in related modules
Not sure what a word means? Check Business Words Made Simple.
Official provider guides
Independent resources, not P.E.A.C.E. partners or recommendations. Check current terms before buying.
- Lovable prompting guidance (opens in a new tab)
Official guidance for describing your project and refining requests.