Verification Checklist
Confirm that every skill from the Lovable module is working before you move on.
Why This Exists
A CA would never sign off on a set of financial statements without running through their review checklist. They might be 95% confident everything is right — but that final 5% check is what separates a professional from someone who guesses.
This checklist works the same way. You have been through the Lovable module. Before you move on, run through every item here. Each one is a concrete, testable action — not a question like "do you feel like you understand it?" Feelings are not evidence. Can you do it? That is the test.
Account and Access
Account Created and Accessible
Open lovable.dev in your browser. Log in with your account. You should land on the dashboard showing your projects list.
Pass: Dashboard loads, your account name or email appears in the top-right corner.
Fail: You cannot log in, or you are taken to the signup page instead of the dashboard. Fix: check your login credentials, confirm your email if you signed up with email, or use the "Forgot Password" option.
Free Tier Understood
Without looking at any guide, answer these three questions from memory:
- Does Lovable require a credit card to use the free tier?
- What happens to your projects when you run out of daily credits?
- Where in the Lovable interface do you find your current credit usage?
Pass: You can answer all three correctly. (Answers: No credit card required. Projects remain accessible, you just cannot make new changes until credits refresh. Credit usage is in the account menu, typically accessible via your profile picture or initials.)
Fail: You are uncertain on any of these. Fix: re-read the Account Setup section and check the current Lovable pricing page.
Building
First Project Created
Open your Lovable dashboard. You should see at least one project card — the one you built during the First Project section.
Pass: At least one project is visible in the dashboard.
Fail: No projects appear. Fix: click New Project and build one using any of the example prompts from the First Project section.
App Generates From a Prompt
Create a new project (or open your existing one) and verify the generation process works end-to-end.
If creating new: type a prompt describing a simple CA-style app — try: "Build a simple client contact list for a CA firm with columns for: client name, company, PAN, email, phone, city, and client type (Individual/Company/Partnership). Design it cleanly with a white background and navy blue headers. Add 5 sample rows with realistic Indian names."
Submit the prompt and wait for generation.
Pass: The preview pane shows a working app that matches what you described. The table has the right columns, the styling is applied, sample data is visible.
Fail: The preview shows a blank screen, an error, or something completely unrelated to your prompt. Fix: try simplifying the prompt to just "Build a simple contact list table with name, email, and phone columns" and rebuild from there.
Prompt Iteration Works
In an existing project, make a specific change request in natural language. Use a concrete instruction like: "Change the table header background to dark navy blue (#1e3a5f) with white text." or "Add a search box above the table that filters rows as you type."
Pass: The preview updates within a few seconds to reflect the change you requested. What you see matches what you asked for.
Fail: The preview does not change, or changes something other than what you specified. Fix: rephrase the instruction to be more specific about which element you are changing and what the new state should look like.
Vague vs. Specific Prompt Difference Understood
Without looking at the Prompting Guide, write down (on paper or in a text file) the five elements of a good Lovable prompt.
Pass: You can name all five: Purpose and Context, Layout and Structure, Data Fields, Visual Style, Sample Data.
Fail: You can only name two or three. Fix: re-read the Prompting Guide section — specifically "The Five Elements of a Great Prompt."
Database Connection
Supabase Project Available
You have a Supabase project ready to connect. You know where to find the Project URL and the Anon Key in the Supabase dashboard.
Without looking at a guide, navigate to your Supabase dashboard and locate both values.
Pass: You can find the Project URL and the Anon (public) key in Supabase → Project Settings → API.
Fail: You cannot find these values. Fix: log into supabase.com, open your project, click the gear icon (Project Settings) in the left sidebar, then click API. The values are in the Project URL and Project API Keys sections.
Connection Attempt Made
You have either successfully connected a Lovable project to Supabase, or you have gone through every step up to the point of connection and understand the process.
If you have connected successfully: the Supabase integration in Lovable shows a connected or success status.
If you did not complete the connection (e.g., you do not have a Supabase project set up yet): you can clearly describe the four steps of the connection process from memory.
Pass (connected): Supabase integration shows a connected status in Lovable.
Pass (process understood): You can describe: find the Supabase integration in Lovable settings → paste the Project URL → paste the Anon Key → save and verify the connection.
Fail: You attempted the connection and got an error you cannot explain. Fix: re-read the Connecting Supabase section, especially the Troubleshooting section at the end.
Data Persistence Understood
Explain in one or two sentences why connecting Supabase makes an app fundamentally different from one with only sample data.
Pass: Your explanation covers the key point: without a database, data is hardcoded and resets on every page load; with Supabase, data is stored permanently, persists across refreshes and devices, and can be read and written by real users.
Fail: You cannot articulate this. Fix: re-read the opening section of Connecting Supabase ("The Problem With Sample Data").
Publishing and Export
Public URL Located and Tested
Open one of your Lovable projects. Find the public URL (via the Share button or the URL visible in the preview pane). Copy it. Open it in a private/incognito browser window.
Pass: The app loads in the private window exactly as it appears in the Lovable editor. It is fully interactive — buttons click, the layout is correct.
Fail: The page does not load, shows an error, or looks different than the editor preview. Fix: check that the project is published (not in draft mode, if Lovable distinguishes between these states). Try opening the URL in a different browser entirely.
Shareable URL Copied and Sent
Send your app URL to someone — a fellow trainee, a WhatsApp contact, or yourself on another device. Confirm they can open it.
Pass: The other person (or you on another device) can open the URL and see the working app.
Fail: The URL does not work for others. Fix: verify you are sharing the full URL including https://. Some messaging apps truncate long URLs — try shortening the URL with a service like bit.ly if needed.
Export Option Located
In your Lovable project, find where the export or GitHub integration option is. You do not need to complete the export — just locate it.
Pass: You can find the Export or GitHub option in the Lovable interface (project settings, top menu, or similar location).
Fail: You cannot find any export option. Fix: re-read the Publishing section under "Downloading and Exporting the Code" and look specifically for buttons labeled Export, Code, or GitHub in the Lovable interface.
Exported Code Structure Understood
Without performing the export, describe what you would expect to find in the exported code folder and why it matters for the training program.
Pass: You can describe: a standard React project structure with src/components, src/pages, a package.json file, and supabase integration code. You understand that the exported code is real React that can be opened in VS Code and continued with Claude Code.
Fail: You cannot describe the exported structure or its significance. Fix: re-read the "What the Exported Code Looks Like" section of the Publishing page.
Final Self-Assessment
Before marking this module complete, answer these honestly:
Can you build a working app from a description in under 30 minutes?
If yes — you have the core skill. Everything else in this module is context and depth that will make you more effective.
If no — go back and build two more projects using the example prompts from the First Project and Prompting Guide sections. The skill comes from repetition, not from reading.
What Comes Next
You now have a working tool for rapid prototyping. Here is how it fits into the larger picture:
Immediately: Use Lovable to prototype Project 1 concepts before committing to a direction. Validate the idea visually before spending time building it properly.
During the full-stack phase: After learning Supabase, come back to Lovable and build a complete data-driven prototype in one session. Then export the code and continue in VS Code.
On real projects: Use Lovable for client presentations and concept validation. Convert to Claude Code-based development for the production version.
The combination of Lovable (speed) + Claude Code (control) + Supabase (data) is one of the most powerful workflows available to a solo developer today. You have just learned the first piece of it.
Module complete when: All checklist items show Pass. If any show Fail, address those specifically before moving on. A half-completed skill creates problems later when you need to rely on it under time pressure.