Build a Portfolio of Three Small Apps You Actually Use

A good vibe-coder portfolio isn't a gallery — it's three tiny apps you open every week. Here is the capstone plan to build yours.

45 min · Reviewed 2026

The Portfolio That Actually Gets Used

Most beginner portfolios are graveyards of half-finished demos. A better measure: three small apps that you open every week because they solve a real problem for you. That is a portfolio that hires itself.

A tracker — something you log daily (workouts, mood, reading, expenses)
A tool — something that replaces a Google Doc you hate (meal planner, trip brain, study flashcards)
A shareable — something other humans touch (a tiny site for a club, a gift, a friend's business)

Layer	Pick	Why
Builder	Lovable or v0 + Cursor	Covers everything vibe coders need
Database	Supabase	Free tier, auth + DB in one
Hosting	Vercel	One-click deploys, preview URLs
Domain	Namecheap or Porkbun	Eight dollars a year each

Capstone plan — 3 weekends, 3 apps. Weekend 1 — Tracker Prompt: "Build me a [habit] tracker with daily logs and monthly charts." Deploy. Use it every day for two weeks. Weekend 2 — Tool Prompt: "Build me a [tool] that replaces the Google Doc I keep copying." Deploy. Use it yourself first. Improve one thing per week. Weekend 3 — Shareable Prompt: "Build a site for [club/gift/friend]." Deploy. Share the URL with three real humans. Listen.This is a real 3-weekend capstone. At the end you have shipped three working apps you and others actually touch.

Post a short write-up of each app on Twitter, LinkedIn, or a personal site
Add a link to each deployed app in your resume or bio
Pick the one with the most pull and go deeper — more features, real users
Teach a friend to vibe-code by cloning one of your repos

The big idea: a vibe-coder's best portfolio isn't polished screenshots, it's three tiny apps you can't stop using. Build those, share them honestly, and doors will open you didn't expect.

End-of-lesson check

8 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-vibecoder-portfolio-of-three

What is the main idea of "Build a Portfolio of Three Small Apps You Actually Use"?
1. A good vibe-coder portfolio isn't a gallery — it's three tiny apps you open every week. Here is the capstone plan to build yours.
2. Use AI as the final authority for the whole decision
3. Avoid checking the answer once it sounds polished
4. Focus only on speed instead of judgment
Which concept is most central to "Build a Portfolio of Three Small Apps You Actually Use"?
1. dogfooding
2. portfolio
3. capstone
4. personal tools
Which use of AI fits this topic best?
1. Let the AI decide what matters without your review
2. Use the answer before checking whether it fits the situation
3. A tracker — something you log daily (workouts, mood, reading, expenses)
4. Treat the AI output as automatically correct
What should a careful learner remember about "Dogfooding is the shortcut"?
1. If you use the app yourself, bugs surface immediately. Apps built for hypothetical users die. Apps built for you, first, survive.
2. Skip the context so the tool can guess faster
3. Treat the output as private even after sharing it online
4. Use the answer without checking the source
You want to use AI after this lesson. What is the safest next step?
1. Act immediately because the AI answer is written clearly
2. Use AI for drafting and comparison, but verify before publishing or relying on it.
3. Hide uncertainty so the final answer looks cleaner
4. Use private or sensitive details before checking permission
How should AI output about portfolio be treated?
1. As proof that no other source is needed
2. As a replacement for context, consent, or expert review
3. As a draft or helper output that still needs human judgment and verification
4. As something that becomes correct when it sounds confident
Name one way to verify an AI answer about portfolio.
Which action would help you apply "Build a Portfolio of Three Small Apps You Actually Use" responsibly?
1. Use the tool to avoid thinking through the tradeoff
2. Keep going even if the output conflicts with a trusted source
3. Treat the AI output as automatically correct
4. A tool — something that replaces a Google Doc you hate (meal planner, trip brain, study flashcards)

← Back to interactive lesson

Tendril · Creators · AI-Assisted Coding

Build a Portfolio of Three Small Apps You Actually Use

A good vibe-coder portfolio isn't a gallery — it's three tiny apps you open every week. Here is the capstone plan to build yours.

45 min · Reviewed 2026

The Portfolio That Actually Gets Used

A tracker — something you log daily (workouts, mood, reading, expenses)
A tool — something that replaces a Google Doc you hate (meal planner, trip brain, study flashcards)
A shareable — something other humans touch (a tiny site for a club, a gift, a friend's business)

Layer	Pick	Why
Builder	Lovable or v0 + Cursor	Covers everything vibe coders need
Database	Supabase	Free tier, auth + DB in one
Hosting	Vercel	One-click deploys, preview URLs
Domain	Namecheap or Porkbun	Eight dollars a year each

Capstone plan — 3 weekends, 3 apps. Weekend 1 — Tracker Prompt: "Build me a [habit] tracker with daily logs and monthly charts." Deploy. Use it every day for two weeks. Weekend 2 — Tool Prompt: "Build me a [tool] that replaces the Google Doc I keep copying." Deploy. Use it yourself first. Improve one thing per week. Weekend 3 — Shareable Prompt: "Build a site for [club/gift/friend]." Deploy. Share the URL with three real humans. Listen.This is a real 3-weekend capstone. At the end you have shipped three working apps you and others actually touch.

Post a short write-up of each app on Twitter, LinkedIn, or a personal site
Add a link to each deployed app in your resume or bio
Pick the one with the most pull and go deeper — more features, real users
Teach a friend to vibe-code by cloning one of your repos

The big idea: a vibe-coder's best portfolio isn't polished screenshots, it's three tiny apps you can't stop using. Build those, share them honestly, and doors will open you didn't expect.

End-of-lesson check

8 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-vibecoder-portfolio-of-three

What is the main idea of "Build a Portfolio of Three Small Apps You Actually Use"?
1. A good vibe-coder portfolio isn't a gallery — it's three tiny apps you open every week. Here is the capstone plan to build yours.
2. Use AI as the final authority for the whole decision
3. Avoid checking the answer once it sounds polished
4. Focus only on speed instead of judgment
Which concept is most central to "Build a Portfolio of Three Small Apps You Actually Use"?
1. dogfooding
2. portfolio
3. capstone
4. personal tools
Which use of AI fits this topic best?
1. Let the AI decide what matters without your review
2. Use the answer before checking whether it fits the situation
3. A tracker — something you log daily (workouts, mood, reading, expenses)
4. Treat the AI output as automatically correct
What should a careful learner remember about "Dogfooding is the shortcut"?
1. If you use the app yourself, bugs surface immediately. Apps built for hypothetical users die. Apps built for you, first, survive.
2. Skip the context so the tool can guess faster
3. Treat the output as private even after sharing it online
4. Use the answer without checking the source
You want to use AI after this lesson. What is the safest next step?
1. Act immediately because the AI answer is written clearly
2. Use AI for drafting and comparison, but verify before publishing or relying on it.
3. Hide uncertainty so the final answer looks cleaner
4. Use private or sensitive details before checking permission
How should AI output about portfolio be treated?
1. As proof that no other source is needed
2. As a replacement for context, consent, or expert review
3. As a draft or helper output that still needs human judgment and verification
4. As something that becomes correct when it sounds confident
Name one way to verify an AI answer about portfolio.
Which action would help you apply "Build a Portfolio of Three Small Apps You Actually Use" responsibly?
1. Use the tool to avoid thinking through the tradeoff
2. Keep going even if the output conflicts with a trusted source
3. Treat the AI output as automatically correct
4. A tool — something that replaces a Google Doc you hate (meal planner, trip brain, study flashcards)

← Back to interactive lesson