Lesson 2 of 16 · 20 min suggested practice
Chat, Plan, and Build: choose the right Lovable mode
Decide when to explore, when to review an implementation plan, and when to let Lovable change the app.
Match the mode to your uncertainty
There are two different questions in a new project: what should the product do, and how should it be implemented? Use Chat for the first question when you are still exploring. For Resource Shelf, discuss whether users need multiple filters or whether one topic filter is enough.
Use Plan when you want Lovable to investigate the existing project and describe how a change will work before editing code. A new data model or an authentication feature deserves this review. Use Build when the behavior is sufficiently clear to implement and verify.
Review a plan as a product owner
Ask the plan to name the pages, data, states, and dependencies affected by a change. For search, it should specify which fields are searched, whether matching ignores case, how search combines with the topic filter, and what appears when nothing matches.
Read the proposal against your acceptance criteria. If it adds a backend to search six static records, ask why that is necessary. If it omits an empty state or reset control, add those requirements before approval. Approving a smaller coherent plan makes the result easier to inspect.
Build one complete slice
For this lesson, implement only the library and detail-page navigation. Build mode can inspect the project, modify files, and verify behavior. Review its summary and file changes, then use the preview yourself. Confirm that the visible result matches the requested behavior rather than relying only on the completion message.
A complete slice includes its important states. A resource detail route should show the right record, provide a route back to the library, and handle an unknown resource ID. Do not postpone every error state until the end of the course.
Recover from a mode mismatch
If you only wanted a discussion and code changed, inspect the change before continuing and use version history when appropriate. If a Plan discussion keeps growing, narrow it to the next user-visible result. If Build makes assumptions you did not intend, name the specific mismatch and supply the missing rule.
The modes share conversation context, but that does not remove the need for precise instructions. Write a brief completion statement for each task: for example, every card opens the correct detail page and an invalid URL shows a helpful not-found screen.
Try this focused prompt.
Plan only: add resource detail routes to Resource Shelf using the current six records. Each card should open its matching detail page with title, topic, description, file format, and download availability. Define the unknown-ID state and return navigation. Reuse existing components and do not introduce a database. After I approve the approach, implement this slice and verify valid routes, an invalid route, and browser back navigation.
Replace the sample context with your own approved facts. Review Lovable’s proposed changes before accepting them.
Evidence before the next step
Check your work.
- You can explain why a task belongs in Chat, Plan, or Build.
- The plan includes dependencies and failure states.
- The implementation is checked against a specific user journey.
Your checkmark stays in this browser. It records your own progress, not a certification.
Official sources & further reading
- Plan a change in Plan mode
- Implement changes in Build mode
- Revert and restore your project with version history
Reviewed November 19, 2026. Plans, terminology and interfaces can change; follow the linked documentation if your workspace differs.