This worksheet does not submit or upload your answers. Refreshing or closing the page clears them. Download your notes to keep a copy. Anything you choose to paste into Lovable is handled by that service.
Choose one task you can observe.
Use the session planner example, or name a similarly small task: turn a packing list into categories, compare three options, or organize a meeting agenda. Finish this sentence: “A person can enter ___ and leave with ___.” Leave login, payments, live AI calls, and shared records for a later project.
For the fictional planner, success means someone selects 30 minutes, enters “practice interview answers,” and receives three steps that total 30 minutes. The agenda uses rules you can inspect. It does not need an AI connection to demonstrate the interaction.
Write the brief before building.
Describe the inputs, result, constraints, and checks. Choose Lovable's Plan mode to review the approach before applying changes. Ask it to flag unclear requirements. Read the proposal and remove anything outside your first version; a longer feature list makes this exercise harder to finish.
A starter brief to adapt
Plan a beginner-friendly practice session planner. User: a learner with one goal and limited time. Inputs: a goal, plus 15, 30, or 60 minutes. Output: three steps whose durations add up to the chosen time, and one reflection question. Use local, explainable rules. No account, database, payments, external API, or hidden submission. Include labels, keyboard access, empty-input feedback, mobile layout, and a Copy plan button. First explain your approach and acceptance checks. Ask about unclear requirements before building.
Build a complete first flow.
Ask Lovable to implement the agreed plan. Try the primary task before adjusting the appearance. Can you enter a goal, choose a duration, generate a plan, and copy it? If something fails, report the exact action, expected result, actual result, and any visible error. Ask for one focused fix and repeat the same check.
Then improve one design decision: readable text, clear button labels, or spacing on a phone. Explain the change in terms of the learner's task. For example: “Keep the time choices visible above the submit button, and make the selected duration clear without relying only on color.”
Try the cases a happy preview hides.
Use an empty goal, a very long goal, and each time option. Confirm that step durations still add up correctly. Navigate with Tab, activate controls with the keyboard, and check visible focus. At a narrow phone width, read the result without sideways scrolling. Enlarge text and ensure controls remain usable.
Refresh the app and observe what happens to its plan. Does the behavior match the brief? Explain any local storage honestly. Because this project uses local rules, it should not need a network request to generate an agenda. If Lovable added accounts, a database, or an external API, pause and review the added behavior before sharing.
Keep the reasoning, not just the result.
Write one thing your first prompt left unclear, one defect you caught, and one choice you would keep. Describe how you know the app helps someone finish the task. If another person tries it, record what they actually do separately from your predictions.
Download the worksheet before leaving. On your next attempt, change one meaningful constraint and repeat the checks. That gives you a comparison you can learn from, instead of a growing list of unfinished features.
Take the next useful lesson.
The AI Superpower learning hub covers the wider Lovable workflow, from planning and design to data, security, publishing, and measurement. Use the free pocket-product kit when you want reusable planning and review tools.
Sources and practice notes
This is an independent AI Teachers exercise. Interface labels and account limits can change. Review Lovable's documentation, Plan mode, and publishing guidance for the current workflow. The fictional session planner is a practice brief, not a prebuilt or production-certified app.