Do I need prior programming experience or a computer science degree?

No degree is needed, but this is not a first-hour coding guide. You should have built at least one small app or landing page with AI help and be comfortable editing files and running commands that an assistant gives you. The guide fills the foundations from that starting point upward.

Can I use any AI tool or do I have to use a specific one?

Any capable assistant works — Cursor, Claude, ChatGPT, Copilot, or similar. The exercises teach you to inspect, test, and correct generated code regardless of the tool, and include prompts that deliberately produce flawed output so you learn to spot assumptions about APIs, async handling, auth, and database queries.

Do I need to pay for hosting, a domain, or a database?

You can complete the core app and local debugging on free tiers. Deployment and custom domain steps use free-tier hosting and a low-cost domain for demonstration; where a provider requires a card, the guide offers a free subdomain alternative and marks the custom domain as optional.

I already started a vibe-coded project — should I abandon it for the capstone app?

Keep it, but build the guide’s capstone app separately. The capstone is intentionally small — one resource, one database table, one auth flow — so each layer can be isolated when it fails. Once you finish, you will apply the same checks and layer-by-layer debugging to your existing project in the final demonstration.

Will this make my AI-generated code secure and production-ready?

It gives you the baseline to avoid the most common failures — exposed secrets, missing server validation, broken auth checks, CORS misconfiguration, and untested migrations — and to verify what AI produces. It does not make you a security specialist; production apps with sensitive data still need deeper hardening and review.

EN2 versions

Software concepts every vibe coder needs to know

Build, deploy, and independently troubleshoot a database-backed web app with login, using AI assistance while correctly identifying which layer — frontend, API, database, or infrastructure — to inspect when something fails.

Fby Finito HQEchipa Finito

Created 3 months agoUpdated last month

Free preview: 3 of 20 steps

Work through them in the real run view, exactly as a buyer does. No account, no payment, nothing saved.

Try it free

Free

3 free unlocks per month — yours to keep forever

Refined across 2 versionsUpdated Aug 2026

Start for free

Try 3 of 20 steps free

No account needed — nothing is saved.

Included with every copy

Your own copy — keep it forever
Gets better over time — free updates included
Run it on web and mobile
Invite a partner to go through it with you — you share the same progress
Make it your own — a private copy you can edit to fit your situation
The playbook's community — ask questions, get additions, and see how other buyers improve it, right on the step

Save

Who it's for

Self-taught beginners who ship features with Cursor, Claude, ChatGPT, or Copilot but get stuck when code breaks outside the happy path and want to understand why

About this playbook

This guide turns AI-assisted tinkering into durable software fundamentals through one small capstone app that grows with each concept. It follows a single codebase from local runtime to deployed production, explaining each layer only when the next hands-on task requires it. Each step pairs a concise model with deliberate practice, including exercises where generated code is made to fail so the failure can be diagnosed and fixed. It does not teach prompting tricks or framework shortcuts, and it does not replace documentation for advanced security, scaling, or DevOps — it builds the transferable mental models needed to direct AI tools correctly and verify their output.

What you'll do, step by stepFree preview

4 phases · 20 steps

Only a sample is open: 3 of 20 steps can be read in full. The rest unlock when you buy.

Phase 1: Master the runtime, terminal, and request cycle
5 steps
Phase 2: Build the data and API core with guided practice
5 steps
Phase 3: Harden and observe the app with varied practice and feedback
5 steps
Phase 4: Ship debug and demonstrate independent capability
5 steps

Try 3 of 20 steps free

Unlock all 20 stepsFree

Details

Estimated duration1 day 3 hours

Steps20

Estimated budget0 EUR — all services used have a free tier

What you need first

A computer with administrator access, a code editor and AI assistant installed, basic comfort copying commands into a terminal, and a free GitHub account