A free open curriculum
Vibe coding means you describe what you want and the AI builds it. No-fibs is the discipline that keeps the vibes honest: the AI never writes a check the app can't cash. Five levels, from your first working button to systems that welcome the audit.
Checkboxes save in this browser only (localStorage) — no account, no tracking, nothing leaves this device.
Vibe coding means you describe what you want and the AI builds it. The first discipline is refusing to ship anything the app can't actually cash. The AI will happily write 'Mark shipped' buttons that don't talk to any real system. Your job is to catch that.
Every button works, every flow finishes
Before you call a feature done, click it in the running app — not in your imagination. If the save doesn't persist, the list doesn't refresh, or the last step dead-ends, the feature isn't done, no matter what the AI told you.
Never let the AI speak for the app
The AI will write marketing copy that promises things the code doesn't do. Read every claim back against the screen. 'Your data is encrypted' is a fib if you never wrote a line of encryption.
Say what's broken out loud
Keep a public known-issues list. A page that admits 'minimap sync is broken' is trusted; a page that hides it is a fib the moment a user hits the bug.
Log what you actually shipped
Keep an append-only build log written by the human — what shipped, what got fixed, what got removed. Never let the AI inflate it.
Graduate when you can honestly check all three
The final lesson isn't on this page
Build one honest thing, put it in the open, and let people hold you to it. When they catch a fib — and they will — go fix it. That loop is the whole school.
The honest fine print