Who makes this

Last updated September 1, 2026

My name is Paolo. I spent my career as a chef and in hospitality operations, and for the last stretch of it I have been building software — not as a hobbyist poking at tutorials, but shipping real systems that real operations depend on, mostly by directing AI agents rather than typing implementation code myself.

That is what this site is about.

Why it exists

Every vibe coding resource I found stopped at the prompt. Here is a wall of text, good luck. None of them showed the part that actually determines whether you ship: the second pass, the third, the moment you notice the model has confidently rewritten something that already worked.

Nobody publishes the failures. So I started writing mine down — what broke, what the tell was, and what the prompt should have said in the first place. This site is that notebook, made public.

What you will find

• The Toolbox — 95 tools in seven categories, each with one plain sentence about what it actually does. No paragraphs.
• The Lexicon — 60 terms from this industry, defined by someone who uses them, with a new one on the front page every day.
• The Stack, Explained — a SaaS as a shopping mall. Entrance, hallways, floors, food court, stockroom. It is how I finally understood it, so it is how I explain it.
• The Titan Audit — a codebase quality rubric scored against the standards of the 28 most valuable companies on earth. Free, in full.

How I work

Coming from kitchens turns out to be an advantage rather than a handicap. A kitchen is a system under load with no tolerance for the excuse that it worked yesterday. Mise en place — everything prepped and on the board before the burner goes on — is exactly the right instinct for prompting an agent. So is the line check: verify before service, not during.

The one rule that governs everything published here: if a model could have written it without me running it, I do not publish it. The prompts carry the date they were tested and which models passed. When I get something wrong, the correction goes on the page.

About the name

Yes, it is a joke. It is also the thesis. A vibrator oscillates; vibe coding oscillates — generate, evaluate, refine, repeat, until the output settles on what you meant. The logo is a waveform that starts wild on the left and damps to a flat line on the right. That is the loop, drawn.

The name gets you to click once. Everything after that has to earn the second visit.

Get in touch

Corrections, arguments, a prompt that failed for you, or a tool that belongs in the toolbox: hello@vibebrator.com.

Broke for you? Say so. Fixed logs are better than clean ones.