Capstone: Build a Real Application
Put everything together โ pick an app idea, build it end-to-end with Claude, and deploy it to the real internet for free
What This Capstone Tests
This is not a quiz โ it is a build. You will use everything from all four levels: effective prompting (Level 0), understanding Claude's capabilities (Level 1), real-world tools (Level 2), and advanced techniques (Level 3). By the end you will have a live application at a real URL, built entirely by directing Claude.
Pick Your App
Choose one of the three ideas below โ each uses the full free-tier stack from Lesson 27 and showcases real Claude capabilities. Or bring your own idea and use these as a template for how to structure your approach.
๐ก App Idea 1: Personal Knowledge Base + AI Q&A
What it does: A private app where you paste articles, notes, and links. You can then ask questions in plain English and Claude searches your notes to answer them.
Stack
- Next.js + Tailwind hosted on Vercel
- Supabase (PostgreSQL + pgvector for semantic search)
- Supabase Auth (only you can access)
- Anthropic API (Haiku for tagging, Sonnet for answers)
Key Features
Starter Prompt for Claude
Build a personal knowledge base app called "Second Brain" with Next.js and Supabase. 1. Auth: Supabase email auth โ only I can sign in 2. Note entry: textarea for pasting text. On save: - Claude (Haiku) generates a 2-sentence summary and 3 tags - Store in: notes(id, content, summary, tags, embedding, created_at) - Generate embedding via Anthropic API and store in pgvector column 3. Search: semantic search using pgvector similarity 4. Q&A page: input โ find top 5 relevant notes โ send to Claude Sonnet with those notes as context โ stream the answer 5. Deploy on Vercel with env vars: NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, ANTHROPIC_API_KEY Start with the database schema, then the note entry UI.
๐ก App Idea 2: Smart Habit Tracker with Weekly AI Coaching
What it does: Track daily habits with a tap. Every Sunday, Claude analyses your week, spots patterns, and sends you a personalised coaching email.
Stack
- Next.js + Tailwind on Vercel
- Supabase (habits + daily logs)
- Clerk auth (free up to 10K users)
- Resend (weekly coaching email)
- Vercel Cron (runs every Sunday 8am)
- Anthropic API (analysis + coaching)
Key Features
Starter Prompt for Claude
Build a habit tracker app called "Momentum" with Next.js, Supabase, and Clerk auth. Database: - habits(id, user_id, name, category, target_days_per_week, created_at) - habit_logs(id, habit_id, user_id, completed_date, created_at) Pages: 1. /dashboard โ today's habits as a checklist (tap to complete) 2. /habits โ manage habits (add/edit/delete) 3. /stats โ 12-week grid per habit (GitHub contribution style) Weekly coaching (Vercel Cron, every Sunday 8am UTC): - API route POST /api/weekly-coach - Pull last 7 days of logs for the user - Send to Claude: completion rates, best/worst habits, streaks - Claude returns a 3-paragraph coaching message - Send email via Resend to user's email Start with database schema, then the dashboard.
๐ก App Idea 3: AI Meeting Prep & Follow-Up Tool
What it does: Before a meeting, paste the agenda and attendees โ Claude drafts talking points. After the meeting, paste your notes โ Claude extracts action items, decisions, and drafts a follow-up email.
Stack
- Next.js + Tailwind on Vercel
- Supabase (meeting history + auth)
- Resend (follow-up emails)
- Anthropic API (prep + follow-up generation)
Key Features
Starter Prompt for Claude
Build a meeting prep app called "Brief" with Next.js and Supabase.
Database:
meetings(id, user_id, title, meeting_date, attendees jsonb,
agenda text, prep_output text, notes text,
structured_output jsonb, followup_email text, created_at)
Flow 1 โ Pre-meeting prep:
- Form: title, date, attendees (name + company), agenda topics
- Call Anthropic API: generate 3 talking points + 2 questions per
agenda topic, and what each attendee likely cares about
- Display and save to database
Flow 2 โ Post-meeting follow-up:
- Textarea for raw notes
- Extract: decisions[], action_items[{task, owner, due}], open_questions[]
- Draft follow-up email (3 paragraphs, professional tone)
- Show structured output + email draft side-by-side
- "Copy email" button
List all meetings at /meetings (title, date, attendee count).
Start with the database schema and pre-meeting flow.How to Run Your Capstone Build
- Create a new GitHub repo and clone it locally
- Run
npx create-next-app@latestin the repo - Create a free Supabase project at supabase.com
- Connect your GitHub repo to Vercel at vercel.com
- Get your Anthropic API key at console.anthropic.com
I'm building [app name] with Next.js 14 App Router, TypeScript, Tailwind CSS, and Supabase. Generate a project CLAUDE.md covering: - Tech stack and versions - Database tables (I'll share schema once built) - Code style: strict TypeScript, no any, Zod for validation - File structure conventions - Patterns to keep consistent across the codebase
Use the starter prompt for your chosen app. Work in this order:
- Database schema (run SQL in Supabase editor)
- Core data layer (Supabase client, TypeScript types)
- Main UI pages (Claude builds component by component)
- API routes (Claude handles the AI integration)
- Auth (last โ once you know what needs protecting)
- Push to GitHub โ Vercel auto-deploys on every push
- Add all env vars in Vercel dashboard โ Settings
- Test the live URL end-to-end
- Run the Lesson 26 security checklist before sharing
Stuck? Prompts That Unblock
Here is the TypeScript error: [paste error] Here is the file: [paste file] Fix the error. Explain what caused it in one sentence.
Expected: [describe] Actual: [describe] Relevant code: [paste] Debug this step by step.
I have [A] working and [B] working separately. I need [A] to trigger [B] when [condition]. Show me the minimal code to wire these together.
Course Complete ๐
If you have built and deployed your capstone, you have done something most daily Claude users have never done. You understand the full stack โ from writing a precise prompt to shipping a production application. You know the pitfalls, the tools, the ecosystem, and the techniques.