LLMs · in Full-stack with Lovable
Claude for Full-stack with Lovable
Product + scope decisions in the Full-stack with Lovable stack. Same role as in the indie-saas stacks — decide what to build before the builder starts iterating. Saves 2 to 3 wrong-direction Lovable cycles.
· 1 weeks ago
Where Claude fits in the workflow
- 1Scope with Claude first
Cheaper to argue with Claude for 20 min than to burn Lovable cycles on the wrong product.
Prompt · Pre-Lovable scoping promptI'm about to build the app below in Lovable. Help me scope it tight before I start prompting. Idea: """ {{1-line product description}} """ Output: 1. **Single core job** — the one thing this app does for the user. One sentence. 2. **3 to 5 screens** for v1, named. 3. **Data model** — tables + columns. Lovable defaults to Supabase. 4. **Auth + billing** — yes / no, what plan tiers if billing. 5. **Out of scope for v1** — 5 things I should NOT build first. 6. **The first prompt for Lovable** — the literal text I should paste into Lovable to get a usable v0.1 in one shot. Be ruthless on scope. The whole point is to ship in a weekend.
Cost in this stack
Free tier
Of the $25/mo weekend mvp budget
Tool pricing
$20/mo Pro · Sonnet API $3/$15 per M tokens (input/output)
Alternatives to Claude at this step
Other tools in the Full-stack with Lovable stack
Other stacks using Claude
See the full Full-stack with Lovable stack
Workflow, costs at three usage tiers, prompts, pitfalls.
Spotted something off?
Wrong price, dead link, stale tool — anything. We review every fix.