Prepare the content and explain how it will be used. Build a version to test and edit before sharing.
Start with a website, educational game, small tool, or dashboard. What matters is who will use it and what they should be able to do. A good description explains behavior and content, as well as colors.
Prepare text, images, and links, with a usage example from opening it to the result. If improving something existing, start with its files and references and specify the part to change.
Choose a suitable building space, such as Sites, Canvas, Artifacts, or a specialized platform, based on the function and publishing needs. Start with a version that does one task. Test it and request a specific fix for the problem you found.
A website preview still needs its links, buttons, inputs, saving, and sharing tested. If it collects data or connects services, define access, permissions, and storage before people rely on it.
Choose from what's available to you. You can use these prompts with several tools. What they can carry out depends on supported features and files.
See tool details and uses in the Tools library →A freelance designer wants a pricing calculator based on design count, revisions, and delivery time. They describe the idea in two lines. AI asks for details and builds it in Lovable or Gemini Canvas. They test it on a phone and fix it until it's ready with a link.
What's been paid, what's outstanding, and a month-end report.
Describe the fields to Lovable or Claude: expense type, amount, date, and client payments. It builds a page you can open on your phone to record them.
Choose a topic to see the explanation, steps, and source.
Prepare content from trusted references and describe the app to Claude or Lovable: a topic list with steps and a source for each. A ready-made prompt is below.
One link to send everyone.
Write the instructions in plain language in chat. Then ask for a simple page that's comfortable on phones and publish it with a link.
For each client: the request's stage, whether it's finished, and their account balance.
The fields are client, work type, stage, and delivery date. Overdue items appear in red.
Items, quantities, and alerts when something is running low.
A system with items, quantities, and prices that alerts you when stock falls below a threshold you set.
Your services or products, WhatsApp orders, and possibly online payment.
Prepare the content in chat, then describe the website to Lovable so it builds and publishes it with a link.
Start with a service page, or a custom tool, or a tracking app depending on what visitors will do.
For metrics and filters, use the dashboard workflow. For sources and comparisons, use the interactive report workflow.
Try an activity that assesses a goal, or a lesson library with sources, practical tasks, and clear navigation.
Open the menu and choose what fits your inputs and desired result. The method's guide appears directly below it.
Prepare the function, content, and visual reference. Ask for a plan of interactions and pages, then a small version that performs the core task in a suitable building space.
Try it on your work: Prepare what you'll work on and start with a small part. Review the result before continuing.
Open any step by its heading. Each explains what to do, why, and what to check before continuing.
A small scope lets you test real value quickly.
Real content reveals design needs before building.
Appearance alone doesn't explain what a button does or where data is saved.
Start with a working flow instead of many parts that only look complete.
A successful preview doesn't mean the link and data work for others.
Open a prompt and fill in your details. Empty fields remain visible so you don't forget them.
Write the prompt in a conversation with the suggested tool after preparing the files listed in the steps.
Copy the prompt as it is, or tailor it with your details first.
Clarifying behavior and inputs helps us build something people can use, beyond just a page's appearance.
Copy the prompt as it is, or tailor it with your details first.
Copy the prompt as it is, or tailor it with your details first.
Test the core function, inputs, links, and saving on phones and computers before sharing the result.
If there's a problem, name the unsuitable part, show an example, and request a specific edit.
