Vibe Coded Today is a reference for people building software by describing it to an AI model rather than by typing every line themselves.

It exists because most of what's written about this is either marketing copy or a thread of screenshots. Neither helps at eleven at night when the model has rewritten your working file for the third time and you want the exact wording that stops it.

What's here

Prompt snippets are copy-paste blocks for a specific job. Planning, debugging, refactoring, shipping, games, and working with AI models directly. Each one is a prompt you can paste and edit.

Guides are longer reads that take a subject end to end, with the prompts included in the right places.

Playbooks build one specific thing from start to finish, whether that's a landing page, a link shortener, a Snake clone or a retrieval-backed search feature.

Fixes are for when something is broken now. Symptom, cause, fix.

What makes it different

Every prompt is a form. Everywhere else, a prompt is a block of text with blanks you have to hunt down and replace by hand. Here, every <placeholder> is a highlighted blank. Click it and type.

It remembers your project. Tell it what you're building, your stack, where it's hosted and which model you use, once. Every prompt on the site fills those in for you, so what you copy is ready to paste. Anything you skip is kept as a <placeholder>, so neither you nor the model misses it.

A prompt with the project details already filled in and three blanks still waiting
The context primer with a project set. Filled blanks sit quietly; the brighter, underlined ones are still waiting for you.
The Your project panel with its four fields filled in
The project panel. Four fields, filled in once, saved only in your browser.

It's a daily paper. A different prompt leads the front page every day, and every page carries the date it was written, so you can judge for yourself how fresh the advice is.

Your project details never leave your device. They're kept in your browser's own storage, and this site never receives them. The privacy policy has the detail.

How it's written

Openly: this site is written with heavy use of AI, by someone who vibe codes for a living. That felt like the only honest way to run a site about vibe coding.

What that means in practice is that a model drafts and I direct, edit, check and correct. Prompts are tested rather than invented. Technical claims about model behaviour and pricing are checked against the published documentation on the day they're written, and the pages carry the date so you can see how old the advice is.

It also means the usual caveat applies here as much as anywhere: check what you read before you rely on it. If something on this site is wrong, tell me and I'll fix it.

Who writes it

Steve, working from the UK. I build things for clients and for myself, mostly on small stacks that one person can hold in their head.

This site is itself vibe coded. It's flat-file PHP with no database, no build step and no framework. Every page you're reading is a Markdown file on disk.

What this site isn't

It isn't affiliated with Anthropic, OpenAI, Google, Cursor or any of the tools it discusses. Nothing here is sponsored. Where a tool is recommended it's because it's the one worth using, and where something is a bad idea the page says so.

Found something wrong, or something missing? Get in touch. Corrections are the most useful thing you can send me.