About Vibe Code Textbook

Vibe Code Textbook is a site about writing software with AI coding agents, written, built, and maintained by one developer who uses them every day and keeps the transcripts. There is no editorial team and no vendor behind it.

What "vibe coding" means here

The phrase started as a joke about letting the model drive. This site takes the tools seriously and the joke lightly: the agents are genuinely useful, they are changing monthly, and most of what is written about them is either marketing or a screenshot with no follow-up. The aim here is to write it down properly.

What is published

Harnesses are walkthroughs of the agent runners themselves: what each one does, how it is configured, what its permission model actually permits, and where it breaks, read from the documentation and the source at a named version.

Workflows are repeatable ways of working with an agent that survived contact with a real codebase: spec-first, tests-first, review loops, context files, and the habits that stop a session going sideways.

Repos worth reading are open-source projects in the agentic-coding space, read at a specific commit, with what they get right and the parts worth borrowing. Star and issue counts carry the date they were read, because they move.

Tutorials build something end to end with an agent and show the prompts, the diffs, and the fixes, including the runs that failed. A failed run is often the more useful article.

Measurements are numbers instead of vibes: tokens, cost, wall-clock time, time-to-green, benchmark results, and exactly how each was collected.

What this site refuses to do

No feature claims that were not checked against the docs or the code. No made-up transcripts. No tool versions left unstated. No "reportedly". If a tool changed after an article was written, the article gets an updated date and a note, not a quiet rewrite. No exclamation marks.

Corrections and counterexamples are welcome and acted on: contact.