The "Remix" Rule
Most people skip planning. They open VS Code or Replit, write three components, realize they don't know how the database connects, and quit.
The Exercise
"My project helps Persondo Taskso they can Benefit."
Don't build Amazon.
That is a 10-year journey. You need a "Single"—a one-hit wonder that solves one specific problem.
Choose Your Player
Manual Coding
You want to understand every line. You love VS Code extensions and debugging in the terminal.
- ✓ Full Control
- ✓ Deep Learning
- ✓ Tech Stack: Next.js, Supabase
AI Assisted
You have the vision, but syntax slows you down. You want to ship by the weekend using AI agents.
- ✓ Insane Speed
- ✓ Focus on Logic, not Syntax
- ✓ Tools: Replit, Lovable, Cursor
The Set List
The Kill List
If it doesn't support the core function, throw it in the trash for v1.
The Napkin Flow
Draw the path. Crucial for AI context.
1. Landing
2. Sign Up
3. Action
4. Success
The Bassline
Before coding, define your Data.
The "God Prompt"
How to talk to Replit/Lovable
Project: Build a [APP TYPE] that allows [USER] to [ACTION].
Tech Stack: React, Tailwind, Supabase.
Style: Minimal, black and white, clean borders.
Core Features:
1. Landing page with hero section.
2. Dashboard with [SPECIFIC COMPONENT].
3. Don't use placeholders, use real data structure.
Data: Create a mock data object for [ITEM].
💡 Tip: Never say "Build me an app." Be specific about the screens and the data.
The MVP Mindset
MVP doesn't mean "broken." It means "focused." Ship one thing that works perfectly.
What MVP Is
THE RIGHT APPROACH
One core loop that delivers value. Users can complete the main action from start to finish.
What MVP Is NOT
COMMON MISTAKES
A half-built version of everything. 10 features at 10% each is worthless.
The Formula
SCOPE = 1
One user. One problem. One solution. Everything else is v2.
// The MVP Test
"Can a user [DO THE THING]
without my help?"
The Timeline
SHIP FAST
If your MVP takes more than a weekend (vibe coding) or a week (manual), you're overbuilding.
// Reality Check
Weekend = Vibe Coding MVP
1 Week = Manual Coding MVP
Remember: The goal is to learn, not to impress. Ship ugly, get feedback, iterate. Perfect is the enemy of shipped.
Common Shipping Mistakes
These mistakes keep projects in "development hell" forever.
Over-Engineering
"I need user roles, admin panel, analytics, and a mobile app." No. You need one working feature.
Design Paralysis
Spending weeks in Figma before writing code. Ship ugly, polish later. Function beats form.
Ship This Week
Set a deadline. Use Shadcn defaults. Deploy to Vercel. Get one real user. That's success.
The Exercises
Complete these before opening your code editor.
The Pitch
One Sentence
- →Write the Remix Rule sentence
- →"X helps Y do Z"
- →If you can't say it simply...
- →...you don't understand it yet
The Kill List
Cut Ruthlessly
- →List ALL features you want
- →Circle only 3 that are essential
- →Cross out everything else
- →That's your v1 scope
The Mode
Choose Your Path
- →Manual: Learn every line
- →Vibe: Ship by weekend
- →Pick ONE. No switching mid-project
- →Set up your tool today
📋 Quick Reference Cheatsheet
The Pitch
"[App] helps [User] do [Task]"MVP Scope
3 features, 4 screens maxShip Timeline
Weekend (Vibe) / 1 Week (Manual)