This guide walks you through shipping capstone v1 in Lovable step by step. You do not write code. You write briefs, review what Lovable builds, and iterate until it is real.

By the end you will have a live URL someone else can open, sign up on, use, and come back to. Plus at least one AI feature that runs in the published app.

Step 1: Start from your seed

• Open your capstone seed (four questions).
• If you only have a one-liner, answer: what it does, who it is for, the one core action, and what you would be proud to demo.
• Narrow until the core action fits in one Lovable session.

Step 2: Write a sharp brief

Read The brief is the new spec first. Your brief needs: what it does, who it is for, one key action, and look and feel in concrete words.

I am building my Week 1 capstone in Lovable.

Product: [one sentence - what it does]
For: [who uses it]
Core action: [the single most important thing a user can do]
Look and feel: [concrete words - e.g. calm, professional, generous spacing, rounded corners]

Ask me any questions you need before you build. Then build one component at a time: start with the core action screen, not the whole app at once.

Step 3: Build in Lovable

1. 1

   New project

   Log in at lovable.dev. Create a new project. Paste your brief.

2. 2

   Build in components

   One screen or flow at a time. Review each piece before asking for the next. Vague whole-app prompts produce generic UI.

3. 3

   Prompt-and-review loop

   When something is wrong, name the layer (frontend, data, auth) and ask for a targeted fix. See Build your app with Lovable.

Step 4: Add auth and data

Your app must remember users. After sign-up, the core action should still be there after a page refresh. That is the proof your data layer works.

Add email and password sign-up and login to my app. Store each user's data so when they log back in they only see their own entries. After you build it, tell me how to test that data survives a page refresh.

Step 5: Add one live AI feature

Enable Lovable AI under Connectors. Pick one feature users can trigger in the live app: summarise, classify, chat, draft, or similar. See AI features for your app.

Add one live AI feature to my published app using Lovable AI:
[e.g. "Summarise the user's input in one sentence" OR "Answer questions from my help docs" OR "Classify this entry as urgent / normal / low"]

Enable Lovable AI under Connectors if needed. The feature must work on the live published URL, not just in preview.

Step 6: Publish and run the stranger test

1. 1

   Publish

   Use the Publish flow or ask Lovable to go live. Remove the watermark before sharing widely. See Ship to a live URL.

2. 2

   Stranger test

   Send the URL to a friend or open it on mobile data (not your logged-in session). They sign up, do the core action, refresh, and confirm data persists.

Publish my app to a live URL. Remove the Lovable watermark if possible. Give me the public URL and a short stranger-test checklist (sign up, do the core action, refresh, confirm data persists).

Step 7: Get cohort feedback

Step 8: Post on LinkedIn

Week 1 of the Agentic AI Builder's Bootcamp with The AI Internship, I just shipped [product name].

What it does: [one sentence, who it's for and the core job]

What I built:
• Sign-up, login, and data that survives a refresh
• Core action: [describe the one thing a user can do]
• AI feature: [name what you shipped]

How: directed the build in Lovable, described what I wanted, reviewed what came back, iterated. No hand-written code this week.

[Attach 2 to 4 screenshots or a 30 to 60s screen recording]

Cohort: feedback welcome in Maven / our WhatsApp group.

#AgenticAI #VibeCoding #TheAIInternship #AIBuilders

Troubleshooting

• Generic UI - add a design brief with tokens (spacing, radius, font) before generating more screens.
• Data lost on refresh - ask Lovable to wire persistence and auth; run the refresh test again.
• AI feature works in preview but not live - confirm Lovable AI is enabled and republish after adding the feature.
• Build feels too big - narrow to one user and one core action; ship v1, iterate in Week 2.