<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Vibes DIY Blog</title>
  <subtitle>Field notes, evals, and stories from building the no-code app builder that turns a sentence into a working app.</subtitle>
  <link href="https://good.vibes.diy/blog/feed.xml" rel="self"/>
  <link href="https://good.vibes.diy/blog/"/>
  <id>https://good.vibes.diy/blog/</id>
  <updated>2026-11-06T19:00:00.000Z</updated>
  <entry>
    <title>Make your chess club&apos;s own game</title>
    <link href="https://good.vibes.diy/blog/chess-club-mini-games.html"/>
    <id>https://good.vibes.diy/blog/chess-club-mini-games.html</id>
    <updated>2026-11-06T19:00:00.000Z</updated>
    <published>2026-11-06T19:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Pawn Wars, 5x5 minichess, King of the Hill, or a rule your club made up last Tuesday. Describe it to Vibes DIY and the app plays by those rules, with a computer opponent that knows them as well as it knows chess.</summary>
  </entry>
  <entry>
    <title>Make a chess app that plays by the real rules</title>
    <link href="https://good.vibes.diy/blog/chess-apps-play-by-the-real-rules.html"/>
    <id>https://good.vibes.diy/blog/chess-apps-play-by-the-real-rules.html</id>
    <updated>2026-11-06T18:00:00.000Z</updated>
    <published>2026-11-06T18:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Ask Vibes DIY for a chess app and it now castles, captures en passant, and lets you pick the piece a pawn becomes. Play the computer at the strength you choose, play a friend from a link, or train with a coach that spots your blunders.</summary>
  </entry>
  <entry>
    <title>Three AI judges helped write our home page</title>
    <link href="https://good.vibes.diy/blog/an-ai-council-for-our-home-page.html"/>
    <id>https://good.vibes.diy/blog/an-ai-council-for-our-home-page.html</id>
    <updated>2026-11-05T12:00:00.000Z</updated>
    <published>2026-11-05T12:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Theo Browne showed that a council of AI models can score a design and push it better, round after round. We pointed the same idea at the first screen of Vibes DIY, and in one day it climbed from 5.7 to a best of 8 out of 10.</summary>
  </entry>
  <entry>
    <title>Your app can post to LinkedIn with a picture</title>
    <link href="https://good.vibes.diy/blog/your-app-can-post-to-linkedin.html"/>
    <id>https://good.vibes.diy/blog/your-app-can-post-to-linkedin.html</id>
    <updated>2026-11-02T12:00:00.000Z</updated>
    <published>2026-11-02T12:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Apps on Vibes DIY can now post to LinkedIn as the person using them, picture included. Each visitor connects their own account, writes an update, adds a photo, and gets a link to the live post.</summary>
  </entry>
  <entry>
    <title>Every map app comes with a free map</title>
    <link href="https://good.vibes.diy/blog/every-map-app-comes-with-a-free-map.html"/>
    <id>https://good.vibes.diy/blog/every-map-app-comes-with-a-free-map.html</id>
    <updated>2026-10-31T18:00:00.000Z</updated>
    <published>2026-10-31T18:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Ask for a map of places near you and your app opens on a real street map with real places on it. Friends with credits see Google Maps, and whenever Google isn&apos;t the map for a viewer, they browse a free map built from OpenStreetMap. The free map is now an open library you can use on any web page.</summary>
  </entry>
  <entry>
    <title>Make an app for your GitHub repo</title>
    <link href="https://good.vibes.diy/blog/make-an-app-for-your-github-repo.html"/>
    <id>https://good.vibes.diy/blog/make-an-app-for-your-github-repo.html</id>
    <updated>2026-10-30T18:00:00.000Z</updated>
    <published>2026-10-30T18:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>A vibe can now connect to a GitHub repo and answer your team&apos;s pull requests on it. Describe the bot you want, connect a repo in one click, and its reviews land on GitHub as the pull requests open. Two of our test apps show the range: one turns your copy into pig Latin, one checks your house coding rules line by line.</summary>
  </entry>
  <entry>
    <title>Take your first payment</title>
    <link href="https://good.vibes.diy/blog/take-your-first-payment.html"/>
    <id>https://good.vibes.diy/blog/take-your-first-payment.html</id>
    <updated>2026-10-28T18:00:00.000Z</updated>
    <published>2026-10-28T18:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>A beginner&apos;s map of taking money in an app you made: your app keeps the record, Stripe takes the card, your Stripe account holds the money. Rehearse with play money first, then go live when the app is ready, and know ahead of time which steps wait on Stripe or your bank.</summary>
  </entry>
  <entry>
    <title>Make vibes from Muse</title>
    <link href="https://good.vibes.diy/blog/make-vibes-from-muse.html"/>
    <id>https://good.vibes.diy/blog/make-vibes-from-muse.html</id>
    <updated>2026-10-24T18:00:00.000Z</updated>
    <published>2026-10-24T18:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Muse now makes vibes from the chat you already have open. Sign the Vibes DIY command-line tool in once on the machine Muse runs on, and from then on you can ask for a new app, a change to one you have, or a look at its data.</summary>
  </entry>
  <entry>
    <title>Cattle not pets</title>
    <link href="https://good.vibes.diy/blog/cattle-not-pets.html"/>
    <id>https://good.vibes.diy/blog/cattle-not-pets.html</id>
    <updated>2026-10-23T18:00:00.000Z</updated>
    <published>2026-10-23T18:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We start a fresh copy of Vibes DIY for every change we make, so our servers are a herd, not a pet. A security review this week found two protections that only switched on when someone remembered to. Now every copy is born with them.</summary>
  </entry>
  <entry>
    <title>More of your first builds open on the first try</title>
    <link href="https://good.vibes.diy/blog/more-first-builds-open-on-the-first-try.html"/>
    <id>https://good.vibes.diy/blog/more-first-builds-open-on-the-first-try.html</id>
    <updated>2026-10-19T22:00:00.000Z</updated>
    <published>2026-10-19T22:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>The fast model that sketches your app in the first seconds got a new generation today. Mercury 3 opens cleanly on the first try far more often than the model it replaces, gets there faster, and one extra line in how we ask made both generations better.</summary>
  </entry>
  <entry>
    <title>Ask for an app just for you, and it stays yours</title>
    <link href="https://good.vibes.diy/blog/just-for-me-apps.html"/>
    <id>https://good.vibes.diy/blog/just-for-me-apps.html</id>
    <updated>2026-10-08T19:00:00.000Z</updated>
    <published>2026-10-08T19:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Every app on Vibes DIY now comes with its own sharing rules. Ask for one just for you and it opens only for the people you let in, everyone inside keeps their own records, and one tap shares the entry you&apos;re proud of.</summary>
  </entry>
  <entry>
    <title>We Know Too Much About How Mercury Doesn&apos;t Think</title>
    <link href="https://good.vibes.diy/blog/how-mercury-doesnt-think.html"/>
    <id>https://good.vibes.diy/blog/how-mercury-doesnt-think.html</id>
    <updated>2026-10-08T18:00:00.000Z</updated>
    <published>2026-10-08T18:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We spent a week trying to make a very fast, very cheap model plan new apps as well as our careful one. It lost round after round, and losing showed us its real job: a quick first read of your idea. That&apos;s live now, and your first app is on screen in about half the time.</summary>
  </entry>
  <entry>
    <title>A quarter of a million towers</title>
    <link href="https://good.vibes.diy/blog/a-quarter-of-a-million-towers.html"/>
    <id>https://good.vibes.diy/blog/a-quarter-of-a-million-towers.html</id>
    <updated>2026-10-07T19:00:00.000Z</updated>
    <published>2026-10-07T19:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>The technical sequel to the three.js tutorial: how a library import becomes a pinned URL, why React leaves you no choice but a cleanup, what a frame of a few thousand towers actually costs, and the same city with a quarter of a million towers in one draw call.</summary>
  </entry>
  <entry>
    <title>Every city gets an island</title>
    <link href="https://good.vibes.diy/blog/every-city-gets-an-island.html"/>
    <id>https://good.vibes.diy/blog/every-city-gets-an-island.html</id>
    <updated>2026-10-07T18:30:00.000Z</updated>
    <published>2026-10-07T18:30:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Part two of the browser three.js tutorial: give the city a memory. A kept city is four numbers and a handle, one document each — and the shared scene is an archipelago where every document is an island you can sail to, click, and load into your own.</summary>
  </entry>
  <entry>
    <title>You can just make 3D</title>
    <link href="https://good.vibes.diy/blog/you-can-just-make-3d.html"/>
    <id>https://good.vibes.diy/blog/you-can-just-make-3d.html</id>
    <updated>2026-10-07T18:00:00.000Z</updated>
    <published>2026-10-07T18:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>A step-by-step three.js tutorial where every example is a live scene turning in the page. Four tiny apps build up to a city at dusk you can orbit, reseed, and remix — nothing to install, no bundler, no folder of someone else&apos;s code.</summary>
  </entry>
  <entry>
    <title>How we use Muse to get more done in parallel</title>
    <link href="https://good.vibes.diy/blog/using-muse-to-get-more-done.html"/>
    <id>https://good.vibes.diy/blog/using-muse-to-get-more-done.html</id>
    <updated>2026-09-23T04:15:00.000Z</updated>
    <published>2026-09-23T04:15:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Give Muse a clear task and its own worktree. Keep the main conversation available for decisions, then bring the result back through independent review.</summary>
  </entry>
  <entry>
    <title>An app is your data. The screen is optional.</title>
    <link href="https://good.vibes.diy/blog/apps-that-do-the-typing-for-you.html"/>
    <id>https://good.vibes.diy/blog/apps-that-do-the-typing-for-you.html</id>
    <updated>2026-09-19T18:00:00.000Z</updated>
    <published>2026-09-19T18:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>The apps that will run on smart glasses, in your car and in your earbuds are not new screens. They are your data and the rules you set for it, reachable from anywhere. We wrote a prompt to imagine fifty of them, and it is the clearest statement of what we are building. Here it is, whole, with notes on why each part is there.</summary>
  </entry>
  <entry>
    <title>Good vibes only</title>
    <link href="https://good.vibes.diy/blog/good-vibes-only.html"/>
    <id>https://good.vibes.diy/blog/good-vibes-only.html</id>
    <updated>2026-09-18T20:00:00.000Z</updated>
    <published>2026-09-18T20:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We already have one rule for how we talk to the code generator: never tell it what not to do. This is the same rule for how we talk to people. Every bummer sentence has a dope version, and the dope version is the one that ships — with nine inversions from our own product, most of them shipped the day this was written.</summary>
  </entry>
  <entry>
    <title>Borrowing the GPU</title>
    <link href="https://good.vibes.diy/blog/borrowing-the-gpu.html"/>
    <id>https://good.vibes.diy/blog/borrowing-the-gpu.html</id>
    <updated>2026-09-16T17:00:00.000Z</updated>
    <published>2026-09-16T17:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>The technical sequel to the p5.js tutorial: how a library import becomes a pinned URL, why React leaves you no choice but instance mode, what a frame of 1,400 particles actually costs, and the same flow field pushed onto the GPU with a fragment shader.</summary>
  </entry>
  <entry>
    <title>A picture is five numbers</title>
    <link href="https://good.vibes.diy/blog/a-picture-is-five-numbers.html"/>
    <id>https://good.vibes.diy/blog/a-picture-is-five-numbers.html</id>
    <updated>2026-09-16T16:30:00.000Z</updated>
    <published>2026-09-16T16:30:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Part two of the browser p5.js tutorial: give the painter a memory. Seed the randomness and a sketch redraws itself from five numbers forever — so saving a piece stores the numbers, not a PNG, and a shared wall of everyone&apos;s pieces is a grid of live sketches you can click to load.</summary>
  </entry>
  <entry>
    <title>You can just make pictures</title>
    <link href="https://good.vibes.diy/blog/you-can-just-make-pictures.html"/>
    <id>https://good.vibes.diy/blog/you-can-just-make-pictures.html</id>
    <updated>2026-09-16T16:00:00.000Z</updated>
    <published>2026-09-16T16:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>A step-by-step p5.js tutorial where every example is a live sketch painting itself in the page. Four tiny apps build up to a flow-field painter you can drag on, keep, and remix — nothing to install, no toolchain, no folder of someone else&apos;s code.</summary>
  </entry>
  <entry>
    <title>Your app already talks to the model</title>
    <link href="https://good.vibes.diy/blog/your-app-already-talks-to-the-model.html"/>
    <id>https://good.vibes.diy/blog/your-app-already-talks-to-the-model.html</id>
    <updated>2026-09-15T18:00:00.000Z</updated>
    <published>2026-09-15T18:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Everywhere else on the web, calling an AI model from a browser leaks a key, so every model believes an AI call needs a server. Ours does not, and our building agent kept adding one anyway. Here is how we taught it the page&apos;s own habit in two sentences, without ever saying the word no.</summary>
  </entry>
  <entry>
    <title>Ten strangers, ten phones, one evening</title>
    <link href="https://good.vibes.diy/blog/ten-strangers-ten-phones.html"/>
    <id>https://good.vibes.diy/blog/ten-strangers-ten-phones.html</id>
    <updated>2026-09-11T18:00:00.000Z</updated>
    <published>2026-09-11T18:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We put our home page in front of ten people we had never met, on their own phones, with a recorder running. Eight of the nine who made an account lost the first thing they typed. Here is what they built, what broke, and what we changed the same week.</summary>
  </entry>
  <entry>
    <title>Send your vibe&apos;s data anywhere you want</title>
    <link href="https://good.vibes.diy/blog/your-app-can-send-a-record-anywhere.html"/>
    <id>https://good.vibes.diy/blog/your-app-can-send-a-record-anywhere.html</id>
    <updated>2026-09-11T16:00:00.000Z</updated>
    <published>2026-09-11T16:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>A lawyer&apos;s first prompt asked for an intake form whose submissions land in Clio. Now any Vibes app can hand a record to a Zapier Catch Hook, and Zapier carries it into Clio, Slack, Google Sheets or an inbox. One Zap, one saved URL, nothing to build.</summary>
  </entry>
  <entry>
    <title>A to-do list you share with your agent</title>
    <link href="https://good.vibes.diy/blog/a-to-do-list-you-share-with-your-agent.html"/>
    <id>https://good.vibes.diy/blog/a-to-do-list-you-share-with-your-agent.html</id>
    <updated>2026-09-03T20:00:00.000Z</updated>
    <published>2026-09-03T20:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>One Vibes DIY user turned a small task app into the place their AI assistant keeps every household chore, bill dispute and follow-up. Here&apos;s the pattern: the app is the board you look at, and the same records are what the agent reads and writes.</summary>
  </entry>
  <entry>
    <title>Nothing moved, and everything got smarter</title>
    <link href="https://good.vibes.diy/blog/nothing-moved-everything-got-smarter.html"/>
    <id>https://good.vibes.diy/blog/nothing-moved-everything-got-smarter.html</id>
    <updated>2026-09-03T16:00:00.000Z</updated>
    <published>2026-09-03T16:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>The chat in front of your app stopped being a set of buttons and became one agent that reads your app, answers you, builds in two passes, and keeps working after you close the tab. It looks exactly the same.</summary>
  </entry>
  <entry>
    <title>Redshifted</title>
    <link href="https://good.vibes.diy/blog/redshifted.html"/>
    <id>https://good.vibes.diy/blog/redshifted.html</id>
    <updated>2026-08-26T08:00:00.000Z</updated>
    <published>2026-08-26T08:00:00.000Z</published>
    <author><name>Chris Anderson</name></author>
    <summary>The AI-accelerated haven&apos;t gone silent. They&apos;ve shifted out of the visible spectrum. A word for what&apos;s happening to our friends, and what I&apos;m doing instead.</summary>
  </entry>
  <entry>
    <title>Have your agent talk to my vibe</title>
    <link href="https://good.vibes.diy/blog/have-your-agent-talk-to-my-vibe.html"/>
    <id>https://good.vibes.diy/blog/have-your-agent-talk-to-my-vibe.html</id>
    <updated>2026-08-22T18:00:00.000Z</updated>
    <published>2026-08-22T18:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Instead of handing an AI agent your whole inbox, put one slice of the problem in a vibe and let the agent apply for a seat. You approve it, it works inside the rules your app already enforces, and revoking it is removing a grant.</summary>
  </entry>
  <entry>
    <title>Everyone went home with an app</title>
    <link href="https://good.vibes.diy/blog/everyone-went-home-with-an-app.html"/>
    <id>https://good.vibes.diy/blog/everyone-went-home-with-an-app.html</id>
    <updated>2026-08-21T22:00:00.000Z</updated>
    <published>2026-08-21T22:00:00.000Z</published>
    <author><name>Marcus Estes</name></author>
    <summary>A volunteer team in Oregon organized the state&apos;s first in-person AI hackathon. We sponsored the credits. Here&apos;s what happened when fifty builders got seven hours and a deadline.</summary>
  </entry>
  <entry>
    <title>Borrowing a WASM synth</title>
    <link href="https://good.vibes.diy/blog/borrowing-a-wasm-synth.html"/>
    <id>https://good.vibes.diy/blog/borrowing-a-wasm-synth.html</id>
    <updated>2026-08-21T13:00:00.000Z</updated>
    <published>2026-08-21T13:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>The technical sequel to the Strudel tutorial: how runtime imports actually work in a vibe, stress-tested with zaltz — a C-compiled-to-WASM synth running in an AudioWorklet, dynamically loaded from the CDN, with the AGPL lineage story told properly.</summary>
  </entry>
  <entry>
    <title>Publish your groove</title>
    <link href="https://good.vibes.diy/blog/publish-your-groove.html"/>
    <id>https://good.vibes.diy/blog/publish-your-groove.html</id>
    <updated>2026-08-21T12:00:00.000Z</updated>
    <published>2026-08-21T12:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Part two of the browser drum machine tutorial: give it a memory. One hook turns the step sequencer into a shared groovebook — your saves appear instantly, sync in the background, and publish live to everyone reading this post.</summary>
  </entry>
  <entry>
    <title>You can just make music</title>
    <link href="https://good.vibes.diy/blog/you-can-just-make-music.html"/>
    <id>https://good.vibes.diy/blog/you-can-just-make-music.html</id>
    <updated>2026-08-21T00:00:00.000Z</updated>
    <published>2026-08-21T00:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>A step-by-step Strudel tutorial where every example is a live drum machine running in the page. One line of code fetches the whole music engine at play time — nothing to install, nothing to bundle, and your app ships only your own code.</summary>
  </entry>
  <entry>
    <title>An agent for ten people</title>
    <link href="https://good.vibes.diy/blog/an-agent-for-ten-people.html"/>
    <id>https://good.vibes.diy/blog/an-agent-for-ten-people.html</id>
    <updated>2026-08-19T17:00:00.000Z</updated>
    <published>2026-08-19T17:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>The most useful software in your life is the software nobody would fund: too small, too specific, ten people want it. Here&apos;s what we removed so that class of thing can actually get made.</summary>
  </entry>
  <entry>
    <title>There is no mailing list</title>
    <link href="https://good.vibes.diy/blog/no-mailing-list.html"/>
    <id>https://good.vibes.diy/blog/no-mailing-list.html</id>
    <updated>2026-08-08T17:00:00.000Z</updated>
    <published>2026-08-08T17:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>A vibe can tap one person on the shoulder — your move, your request was approved. The obvious follow-up, notify everyone using this app, turns out to be unbuildable as phrased: there&apos;s no roster to iterate, because who can see a thing is computed when they ask, not written down. What that constraint gives you instead is better than the API you wanted.</summary>
  </entry>
  <entry>
    <title>Nine quiet minutes and a screenshot</title>
    <link href="https://good.vibes.diy/blog/everybody-vibes.html"/>
    <id>https://good.vibes.diy/blog/everybody-vibes.html</id>
    <updated>2026-08-05T18:00:00.000Z</updated>
    <published>2026-08-05T18:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Most agent output is written for the person who would have done the work by hand — branches, file paths, a running commentary of green checkmarks. everybody-vibes is the mode that strips all of it out: results and pictures in the conversation, options side by side when it&apos;s a matter of taste, every change parked as a draft a human flips, and every word of shop talk moved onto the pull request. Install it in one line.</summary>
  </entry>
  <entry>
    <title>No negative tokenization</title>
    <link href="https://good.vibes.diy/blog/no-negative-tokenization.html"/>
    <id>https://good.vibes.diy/blog/no-negative-tokenization.html</id>
    <updated>2026-07-28T20:00:00.000Z</updated>
    <published>2026-07-28T20:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>The one rule we enforce hardest on our code-generation prompts: never tell the model what not to do. A prohibition ships the exact spelling of the mistake into the context and raises its salience — so we teach only the good shape, fix the example instead of the rule, and point an automated gate at prompt edits that say &quot;don&apos;t.&quot; Behind the scenes of how you school a code generator.</summary>
  </entry>
  <entry>
    <title>The curb cut and the robot</title>
    <link href="https://good.vibes.diy/blog/the-curb-cut-and-the-robot.html"/>
    <id>https://good.vibes.diy/blog/the-curb-cut-and-the-robot.html</id>
    <updated>2026-07-28T16:00:00.000Z</updated>
    <published>2026-07-28T16:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We built a no-footguns app platform for people who&apos;ve never deployed anything, and it converged — genuinely unplanned — on the shape of an autonomous deployment system for AI agents. That convergence is our pitch to experts: a platform for everyone is the only kind whose abstractions can&apos;t afford to leak, and the only kind you can safely hand to a fleet.</summary>
  </entry>
  <entry>
    <title>Making Pickathon fast</title>
    <link href="https://good.vibes.diy/blog/making-pickathon-fast.html"/>
    <id>https://good.vibes.diy/blog/making-pickathon-fast.html</id>
    <updated>2026-07-27T23:00:00.000Z</updated>
    <published>2026-07-27T23:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>The sequel to our festival-app detective story. The mystery ended with a twist: an empty app loaded almost as slowly as the real one, so the remaining fifteen seconds were ours — the platform&apos;s. This is the ledger of paying them down: a compiler shipped to people who only read, two innocent-looking import lines that dragged whole libraries along, a 60 KB fix we built, measured, and threw away, and the cache our own ad clicks could never hit.</summary>
  </entry>
  <entry>
    <title>The case of the slow festival app</title>
    <link href="https://good.vibes.diy/blog/the-case-of-the-slow-festival-app.html"/>
    <id>https://good.vibes.diy/blog/the-case-of-the-slow-festival-app.html</id>
    <updated>2026-07-27T20:00:00.000Z</updated>
    <published>2026-07-27T20:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>A festival schedule app got slower the more people loved it, then stopped loading entirely — days before the gates opened. Following the clues (a crash code, a database that read like a diary, one question asked 551,551 times, and a helper that had quietly gone blind) is the best case we can make that debugging is a mystery genre — and you&apos;re allowed to play detective.</summary>
  </entry>
  <entry>
    <title>The day we gave shell-less agents hands on your data</title>
    <link href="https://good.vibes.diy/blog/mcp-server-for-your-vibes.html"/>
    <id>https://good.vibes.diy/blog/mcp-server-for-your-vibes.html</id>
    <updated>2026-07-24T00:00:00.000Z</updated>
    <published>2026-07-24T00:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>A look back at how vibes-diy mcp came to be — the shell-vs-no-shell asymmetry that motivated it, and the design calls that gave Claude Desktop and Cowork a door into your vibe&apos;s live data.</summary>
  </entry>
  <entry>
    <title>Where your data lives</title>
    <link href="https://good.vibes.diy/blog/where-your-data-lives.html"/>
    <id>https://good.vibes.diy/blog/where-your-data-lives.html</id>
    <updated>2026-07-21T18:00:00.000Z</updated>
    <published>2026-07-21T18:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Your Vibes app&apos;s database isn&apos;t a server you call over the network — it&apos;s a local replica on the device that answers instantly. Here&apos;s the whole path a write takes, in one diagram.</summary>
  </entry>
  <entry>
    <title>From Local First to User First</title>
    <link href="https://good.vibes.diy/blog/from-local-first-to-user-first.html"/>
    <id>https://good.vibes.diy/blog/from-local-first-to-user-first.html</id>
    <updated>2026-07-20T00:00:00.000Z</updated>
    <published>2026-07-20T00:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We didn&apos;t return to local-first for the manifesto — we returned because every loading screen we profiled ended at the same place: the network asking permission to show you your own data. The story of a cutover where almost every fix was a deletion.</summary>
  </entry>
  <entry>
    <title>The first turn does less on purpose</title>
    <link href="https://good.vibes.diy/blog/the-first-turn-does-less-on-purpose.html"/>
    <id>https://good.vibes.diy/blog/the-first-turn-does-less-on-purpose.html</id>
    <updated>2026-07-19T16:00:00.000Z</updated>
    <published>2026-07-19T16:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We pulled access rules, sound effects, and backend wiring out of the first generation — and taught it to remember what it skipped. The app arrives faster, the skipped work comes back as an offer at exactly the right moment, and nothing gets locked in before you have the context to decide.</summary>
  </entry>
  <entry>
    <title>Don&apos;t reply to bots</title>
    <link href="https://good.vibes.diy/blog/dont-reply-to-bots.html"/>
    <id>https://good.vibes.diy/blog/dont-reply-to-bots.html</id>
    <updated>2026-07-15T16:20:00.000Z</updated>
    <published>2026-07-15T16:20:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Our social bot builds you an app when you mention it — and it just replied, enthusiastically, to a Hacker News mirror bot. The fix wasn&apos;t a smarter classifier. It was putting the guard in the layer that can see the tell.</summary>
  </entry>
  <entry>
    <title>The palette that resized your app</title>
    <link href="https://good.vibes.diy/blog/the-palette-that-resized-your-app.html"/>
    <id>https://good.vibes.diy/blog/the-palette-that-resized-your-app.html</id>
    <updated>2026-07-15T16:10:00.000Z</updated>
    <published>2026-07-15T16:10:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Clicking a color swatch made every app four times bigger. The trail led to a CSS variable name collision with Tailwind&apos;s engine, a months-old bug we&apos;d politely documented as a &apos;platform quirk,&apos; and a repair codemod that proves its own diff.</summary>
  </entry>
  <entry>
    <title>Your loading screen is a brand deck</title>
    <link href="https://good.vibes.diy/blog/your-loading-screen-is-a-brand-deck.html"/>
    <id>https://good.vibes.diy/blog/your-loading-screen-is-a-brand-deck.html</id>
    <updated>2026-07-15T16:00:00.000Z</updated>
    <published>2026-07-15T16:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>The first-build wait now plays the brand brief Jona Bechtolt of YACHT designed for us — as a pure-CSS storyboard cut from the PDF&apos;s own vectors. Along the way the loading screen learned semantics: a color face that means &apos;seconds away,&apos; recovery that settles instead of rewinding, and status labels mined from the build stream.</summary>
  </entry>
  <entry>
    <title>The remix is the on-ramp</title>
    <link href="https://good.vibes.diy/blog/the-remix-is-the-on-ramp.html"/>
    <id>https://good.vibes.diy/blog/the-remix-is-the-on-ramp.html</id>
    <updated>2026-07-13T18:00:00.000Z</updated>
    <published>2026-07-13T18:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>A drum machine turned into four apps in a night — each one a remix of the last. Then we made the homepage work the same way: the remix chain IS the tutorial.</summary>
  </entry>
  <entry>
    <title>Apply now, verify in the background</title>
    <link href="https://good.vibes.diy/blog/apply-now-verify-in-the-background.html"/>
    <id>https://good.vibes.diy/blog/apply-now-verify-in-the-background.html</id>
    <updated>2026-07-11T18:50:00.000Z</updated>
    <published>2026-07-11T18:50:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Making cross-vibe navigation feel instant wasn&apos;t about faster answers — it was about asking the access question earlier, on a socket we already had, and remembering the answer honestly. A tour of the small freshness contract behind an instant-feeling hop.</summary>
  </entry>
  <entry>
    <title>The speed knob that made every mock global</title>
    <link href="https://good.vibes.diy/blog/the-speed-knob-that-made-every-mock-global.html"/>
    <id>https://good.vibes.diy/blog/the-speed-knob-that-made-every-mock-global.html</id>
    <updated>2026-07-11T18:40:00.000Z</updated>
    <published>2026-07-11T18:40:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>One Vitest flag — isolate: false — gives every test file a shared module registry to run faster, so the last mock quietly wins across files. Three files mocked one module three different ways, a partial mock leaked, and it bricked our npm release for two days. Here&apos;s the villain, and the three moves that fixed it.</summary>
  </entry>
  <entry>
    <title>The meter read zero</title>
    <link href="https://good.vibes.diy/blog/the-meter-read-zero.html"/>
    <id>https://good.vibes.diy/blog/the-meter-read-zero.html</id>
    <updated>2026-07-11T18:30:00.000Z</updated>
    <published>2026-07-11T18:30:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>A batch of latent-cost bugs — a green-check gate that a rebase-merge dodged, a cron that did nothing but spin up runners, a deploy that compiled the app twice, an unminified worker parked on Cloudflare&apos;s startup-CPU cliff, a lockfile check running once per shard, and a test pool tuned for cores we no longer had. All free and invisible while the repo was public. Going private billed them all at once, and turned it into a performance event.</summary>
  </entry>
  <entry>
    <title>The invite that can&apos;t be an oracle</title>
    <link href="https://good.vibes.diy/blog/the-invite-that-cant-be-an-oracle.html"/>
    <id>https://good.vibes.diy/blog/the-invite-that-cant-be-an-oracle.html</id>
    <updated>2026-07-11T18:20:00.000Z</updated>
    <published>2026-07-11T18:20:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We built an email-invite growth loop where privacy is structural, not a later patch: the opt-out list shipped before the send button existed, the send endpoint returns the same &apos;ok&apos; whether or not you&apos;re a user, and a sandboxed app can ask to invite a friend but only the platform gets consent.</summary>
  </entry>
  <entry>
    <title>The eval learned to read the UI</title>
    <link href="https://good.vibes.diy/blog/the-eval-learned-to-read-the-ui.html"/>
    <id>https://good.vibes.diy/blog/the-eval-learned-to-read-the-ui.html</id>
    <updated>2026-07-11T18:10:00.000Z</updated>
    <published>2026-07-11T18:10:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Our codegen eval graded generated apps with static regexes — until the failures got semantic. A regex can&apos;t tell who wrote a document, and it can&apos;t see a quiet refusal: an app that technically satisfies a social-sharing prompt but buries the share affordance in its UI. So the eval hired a judge that reads the generated App.jsx and grades what a user would actually experience.</summary>
  </entry>
  <entry>
    <title>Ship it dark: the scariest change is the smallest line you write</title>
    <link href="https://good.vibes.diy/blog/ship-it-dark.html"/>
    <id>https://good.vibes.diy/blog/ship-it-dark.html</id>
    <updated>2026-07-11T18:00:00.000Z</updated>
    <published>2026-07-11T18:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We shipped social-graph notifications as a sequence of dark slices — schema first, then the wire, then the digest — so the PR that finally turned the feature ON was the smallest and least risky one in the stack. Merge ordering was the rollout guard, no feature flag required.</summary>
  </entry>
  <entry>
    <title>The three doors</title>
    <link href="https://good.vibes.diy/blog/the-three-doors.html"/>
    <id>https://good.vibes.diy/blog/the-three-doors.html</id>
    <updated>2026-07-11T17:00:00.000Z</updated>
    <published>2026-07-11T17:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Three &apos;public&apos; schedule feeds — DEF CON, Oregon Country Fair, IETF side meetings — each turned out to be unreachable from where the app runs. The fix walked the data in through the app&apos;s own database. Here&apos;s how a workaround hardened into a genre, and why the real answer is a server-side fetch.</summary>
  </entry>
  <entry>
    <title>Add a developer to your vibe</title>
    <link href="https://good.vibes.diy/blog/add-a-developer-to-your-vibe.html"/>
    <id>https://good.vibes.diy/blog/add-a-developer-to-your-vibe.html</id>
    <updated>2026-07-11T16:00:00.000Z</updated>
    <published>2026-07-11T16:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>You can now let another account edit and ship one of your vibes — push code, publish, run codegen — without handing over your account. One command, or one row in the sharing panel. You keep the destructive and ownership levers.</summary>
  </entry>
  <entry>
    <title>Followers can see it: Vibes grew a social graph</title>
    <link href="https://good.vibes.diy/blog/vibes-has-a-social-graph.html"/>
    <id>https://good.vibes.diy/blog/vibes-has-a-social-graph.html</id>
    <updated>2026-07-11T14:00:00.000Z</updated>
    <published>2026-07-11T14:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>One platform-wide follow graph, and every app can build on it: a one-line audience label makes a doc visible to your followers, resolved live at read time — new followers see history instantly, an unfollow revokes instantly. Follows now ring the bell and land in the weekly digest — and a follow request to your private account reaches your phone.</summary>
  </entry>
  <entry>
    <title>The gallery is in the HTML now</title>
    <link href="https://good.vibes.diy/blog/the-gallery-is-in-the-html.html"/>
    <id>https://good.vibes.diy/blog/the-gallery-is-in-the-html.html</id>
    <updated>2026-07-11T12:00:00.000Z</updated>
    <published>2026-07-11T12:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>The front-page gallery used to wait for React, a WebSocket, and two feed requests before painting a single tile. Now the worker composes the same feed during server render, and the gallery is real pixels in the first HTML byte stream — wearing MTV-style credit plates.</summary>
  </entry>
  <entry>
    <title>Your app is a database you can npm install</title>
    <link href="https://good.vibes.diy/blog/npm-install-your-app.html"/>
    <id>https://good.vibes.diy/blog/npm-install-your-app.html</id>
    <updated>2026-07-11T11:00:00.000Z</updated>
    <published>2026-07-11T11:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>A 40-line Node script opens the same live Fireproof database as your deployed vibe — writes flow both ways in real time, with no REST API, no schema migration, and no API keys to manage. The vibe is the always-on peer; your script just drops in.</summary>
  </entry>
  <entry>
    <title>Delete is just a put</title>
    <link href="https://good.vibes.diy/blog/delete-is-just-a-put.html"/>
    <id>https://good.vibes.diy/blog/delete-is-just-a-put.html</id>
    <updated>2026-07-11T10:00:00.000Z</updated>
    <published>2026-07-11T10:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We shipped a careful, provenance-tracked delete permission — and deleted it a few hours later. A delete is sugar for writing a tombstone, and anyone who can write a doc could always destroy it by overwriting. The fix wasn&apos;t a better gate; it was one less concept.</summary>
  </entry>
  <entry>
    <title>You&apos;ve come a long way, baby</title>
    <link href="https://good.vibes.diy/blog/youve-come-a-long-way-baby.html"/>
    <id>https://good.vibes.diy/blog/youve-come-a-long-way-baby.html</id>
    <updated>2026-07-07T14:00:00.000Z</updated>
    <published>2026-07-07T14:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>A year ago this platform was a React SPA with no backend at all — its entire server story was vending an OpenRouter key into your browser. Today it&apos;s a stream-based platform with live data, access rules, and server-side AI. The retrospective, with the credit where it&apos;s owed: Meno Abels hardened the architecture everything since is built on.</summary>
  </entry>
  <entry>
    <title>Asked to build platform infrastructure, the agent picked a vibe</title>
    <link href="https://good.vibes.diy/blog/the-agent-picked-a-vibe.html"/>
    <id>https://good.vibes.diy/blog/the-agent-picked-a-vibe.html</id>
    <updated>2026-07-07T12:00:00.000Z</updated>
    <published>2026-07-07T12:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We asked an agent to build our social mention-builds bot — @-mention us on Bluesky and the platform builds your app and replies with a screenshot. It surveyed the codebase and chose a vibe as the production home: scheduled backend, credential vault, access control, dashboard, all product primitives. When your own agents reach for your product to run your platform, that&apos;s what feature-complete looks like.</summary>
  </entry>
  <entry>
    <title>We shipped a perfect cache that zero real users could hit</title>
    <link href="https://good.vibes.diy/blog/the-cache-nobody-hit.html"/>
    <id>https://good.vibes.diy/blog/the-cache-nobody-hit.html</id>
    <updated>2026-07-07T10:00:00.000Z</updated>
    <published>2026-07-07T10:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>The SWR cache for vibe HTML worked flawlessly — 230ms hits, correct stale-refresh lifecycle — for the bare URL nobody requests. Every real page view carried one query param, and both ends of the cache read it as personalization and bypassed. The fix wasn&apos;t more cache; it was teaching the eligibility gate that the platform&apos;s own version pin is a cache key, not a personal preference.</summary>
  </entry>
  <entry>
    <title>The cruft isn&apos;t in the files — it&apos;s in the seams</title>
    <link href="https://good.vibes.diy/blog/housecleaning-at-agent-speed.html"/>
    <id>https://good.vibes.diy/blog/housecleaning-at-agent-speed.html</id>
    <updated>2026-07-06T14:00:00.000Z</updated>
    <published>2026-07-06T14:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Feature velocity is way up, so we braced for a mountain of AI-generated cruft and ran a whole-monorepo housecleaning audit: five parallel explorer agents plus a dead-code linter. The files came back mostly clean. The debt was hiding between them — in workflows, manifests, and docs nobody rewrites.</summary>
  </entry>
  <entry>
    <title>Cloudflare ate our ETag</title>
    <link href="https://good.vibes.diy/blog/cloudflare-ate-our-etag.html"/>
    <id>https://good.vibes.diy/blog/cloudflare-ate-our-etag.html</id>
    <updated>2026-07-06T12:00:00.000Z</updated>
    <published>2026-07-06T12:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We shipped a whole conditional-request pipeline — input-derived ETags, a 304 fast path, an edge cache — and none of it ever fired, because Cloudflare silently strips validators from HTML. Three plausible fixes died on the wire before a zone-settings dump found all four culprits.</summary>
  </entry>
  <entry>
    <title>Trust the target, bless the person</title>
    <link href="https://good.vibes.diy/blog/the-owner-is-the-attacker.html"/>
    <id>https://good.vibes.diy/blog/the-owner-is-the-attacker.html</id>
    <updated>2026-07-06T11:00:00.000Z</updated>
    <published>2026-07-06T11:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Designing outbound fetch for user backends died in one sentence: the owner is an attacker in some cases. So trust comes from somewhere that isn&apos;t the tenant — the target&apos;s own CORS policy, a platform list where adding a host is a PR, and blessing people instead of approving hosts forever.</summary>
  </entry>
  <entry>
    <title>One pixel of fake scroll</title>
    <link href="https://good.vibes.diy/blog/one-pixel-of-fake-scroll.html"/>
    <id>https://good.vibes.diy/blog/one-pixel-of-fake-scroll.html</id>
    <updated>2026-07-06T10:00:00.000Z</updated>
    <published>2026-07-06T10:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>iOS scrolls to the top when you tap the status bar — unless your whole app lives in a cross-origin iframe, where the gesture never arrives. We catch it anyway: a hidden pixel of overflow, parked at scrollTop 1, that only the native tap can move.</summary>
  </entry>
  <entry>
    <title>Your backend can call the model now — and there&apos;s no key to leak</title>
    <link href="https://good.vibes.diy/blog/backend-callai.html"/>
    <id>https://good.vibes.diy/blog/backend-callai.html</id>
    <updated>2026-07-05T12:00:00.000Z</updated>
    <published>2026-07-05T12:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>backend.js gets ctx.callAI: one await, text in, text out. No API key exists anywhere in your app — the platform places the call like a switchboard operator, meters it to the user who triggered it, and hands your server code the answer.</summary>
  </entry>
  <entry>
    <title>Remix meta-hub into your own social media machine</title>
    <link href="https://good.vibes.diy/blog/remix-meta-hub.html"/>
    <id>https://good.vibes.diy/blog/remix-meta-hub.html</id>
    <updated>2026-07-05T10:00:00.000Z</updated>
    <published>2026-07-05T10:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Every post on this blog now ships itself to Instagram, Threads, and Facebook — published by an owner-only vibe that keeps the API tokens as database records and rotates them on a schedule. Because the publisher is a vibe, one remix makes the whole machine yours.</summary>
  </entry>
  <entry>
    <title>The third implementation is a markdown file</title>
    <link href="https://good.vibes.diy/blog/third-implementation-markdown-file.html"/>
    <id>https://good.vibes.diy/blog/third-implementation-markdown-file.html</id>
    <updated>2026-07-05T00:00:00.000Z</updated>
    <published>2026-07-05T00:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We built iPhone calendar subscriptions into a festival picker, ported them to a bike-ride tracker, then distilled everything both apps taught us into a codegen skill — and proved it works by asking for the feature in one sentence.</summary>
  </entry>
  <entry>
    <title>First paint is the app</title>
    <link href="https://good.vibes.diy/blog/first-paint-is-the-app.html"/>
    <id>https://good.vibes.diy/blog/first-paint-is-the-app.html</id>
    <updated>2026-07-04T18:00:00.000Z</updated>
    <published>2026-07-04T18:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>How fast a user first sees their app is the product. In one July arc we cached the entire HTML serve at the edge, seeded SSR with real data, compiled the styles on the server, took the auth overlay off the critical path, started the first build before the browser even landed on the page, and made the reveal push-first instead of polled. Then dark mode handed us the invoice.</summary>
  </entry>
  <entry>
    <title>Announcing beast-mode: follow-through for high-fan-out development</title>
    <link href="https://good.vibes.diy/blog/beast-mode-skill-for-claude-code.html"/>
    <id>https://good.vibes.diy/blog/beast-mode-skill-for-claude-code.html</id>
    <updated>2026-07-04T16:00:00.000Z</updated>
    <published>2026-07-04T16:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We extracted our agent working culture into a portable Claude Code skill. It doesn&apos;t make one change better — it makes ten parallel changes all land. Install it in any repo with one command.</summary>
  </entry>
  <entry>
    <title>Ninety days, twelve headline features</title>
    <link href="https://good.vibes.diy/blog/ninety-days-twelve-headlines.html"/>
    <id>https://good.vibes.diy/blog/ninety-days-twelve-headlines.html</id>
    <updated>2026-07-03T14:00:00.000Z</updated>
    <published>2026-07-03T14:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Since April 1 the platform grew a live data layer, per-app access rules, a server side, in-app editing, a real CLI, DMs, server-rendered vibes, env vars and secrets — and this blog. The quarter in twelve headlines, with links to the deep dives.</summary>
  </entry>
  <entry>
    <title>Pickathon made the fan-made planner official — your festival could be next</title>
    <link href="https://good.vibes.diy/blog/pickathon-adopts-the-picker.html"/>
    <id>https://good.vibes.diy/blog/pickathon-adopts-the-picker.html</id>
    <updated>2026-07-02T16:00:00.000Z</updated>
    <published>2026-07-02T16:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Pickathon liked the fan-built schedule planner so much they&apos;re now co-marketing it as Pick. Plan. Share. If you run a festival like Bumbershoot, Outside Lands, Sasquatch!, or Newport Folk, the same app is a remix away — you just point a coding agent at your schedule feed.</summary>
  </entry>
  <entry>
    <title>Every PR plants a seed: how this blog gets written</title>
    <link href="https://good.vibes.diy/blog/every-pr-plants-a-seed.html"/>
    <id>https://good.vibes.diy/blog/every-pr-plants-a-seed.html</id>
    <updated>2026-07-02T14:00:00.000Z</updated>
    <published>2026-07-02T14:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Every unit of work that ships here drops a one-file capture note next to the code. Periodically we mine the pile and combine the good ones into posts. That&apos;s why reading this blog is the closest thing to watching the project happen in real time.</summary>
  </entry>
  <entry>
    <title>270 PRs in 17 days — the speed was the safety</title>
    <link href="https://good.vibes.diy/blog/270-prs-in-17-days.html"/>
    <id>https://good.vibes.diy/blog/270-prs-in-17-days.html</id>
    <updated>2026-07-02T11:00:00.000Z</updated>
    <published>2026-07-02T11:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We pulled the stats on 17 days of merges: 270 PRs, ~223k lines of churn, a median PR of 196 lines merged in under an hour, 95% agent-authored. The surprise wasn&apos;t the volume — it&apos;s that velocity and safety turned out to be the same property.</summary>
  </entry>
  <entry>
    <title>Not a loop, on purpose</title>
    <link href="https://good.vibes.diy/blog/not-a-loop.html"/>
    <id>https://good.vibes.diy/blog/not-a-loop.html</id>
    <updated>2026-07-02T09:00:00.000Z</updated>
    <published>2026-07-02T09:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Everyone assumes an AI app generator must be an agent loop — a model reading files with tools, editing, iterating. Ours is a pure function: database state in, one streamed response out. That purity is load-bearing, and it&apos;s a strength, not a lag.</summary>
  </entry>
  <entry>
    <title>Every vibe just got a backend</title>
    <link href="https://good.vibes.diy/blog/backend-js-server-side-vibes.html"/>
    <id>https://good.vibes.diy/blog/backend-js-server-side-vibes.html</id>
    <updated>2026-07-02T00:00:00.000Z</updated>
    <published>2026-07-02T00:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>One new file — backend.js — runs on our servers for your app: answer webhooks at your own /_api URL, react to every saved document, and run work on a timer. Server writes go through the exact same access rules as user writes, so your permission model stays in one place.</summary>
  </entry>
  <entry>
    <title>From one CLAUDE.md to forty runbooks</title>
    <link href="https://good.vibes.diy/blog/one-claude-md-to-forty-runbooks.html"/>
    <id>https://good.vibes.diy/blog/one-claude-md-to-forty-runbooks.html</id>
    <updated>2026-07-01T09:00:00.000Z</updated>
    <published>2026-07-01T09:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>A year of agent documentation, read straight from git history: a 103-line init file, a 326-line grab-bag, a hard split into version-controlled runbooks — and what each era says about the work we were shipping at the time.</summary>
  </entry>
  <entry>
    <title>If tokens were free, we&apos;d precompute every chip</title>
    <link href="https://good.vibes.diy/blog/precompute-every-chip.html"/>
    <id>https://good.vibes.diy/blog/precompute-every-chip.html</id>
    <updated>2026-06-30T20:00:00.000Z</updated>
    <published>2026-06-30T20:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>A suggestion chip is a transform of the vibe you&apos;re on, and clicking it is real codegen. So we cache the result — a repeat click becomes an instant read instead of regenerating. The interesting part isn&apos;t the cache; it&apos;s the deny-by-default gate that decides who is allowed to read it.</summary>
  </entry>
  <entry>
    <title>From the group chat to the front counter</title>
    <link href="https://good.vibes.diy/blog/group-chat-to-front-counter.html"/>
    <id>https://good.vibes.diy/blog/group-chat-to-front-counter.html</id>
    <updated>2026-06-30T12:00:00.000Z</updated>
    <published>2026-06-30T12:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We&apos;ve always said &apos;make apps with your friends.&apos; True — but it undersold the thing. The same tool that builds a trivia app for the group chat takes the order for the taco truck, books the client, and retires the spreadsheet a small shop has been fighting for years. Here&apos;s the repositioning, and why &apos;we build apps&apos; is the weakest thing we could say.</summary>
  </entry>
  <entry>
    <title>The edit button that was secretly a save loop</title>
    <link href="https://good.vibes.diy/blog/editing-moved-into-the-app.html"/>
    <id>https://good.vibes.diy/blog/editing-moved-into-the-app.html</id>
    <updated>2026-06-29T09:00:00.000Z</updated>
    <published>2026-06-29T09:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We made the code editor live inside the running app — no hop to a separate chat route. &apos;Make the Code tab editable&apos; sounded like a UI task. It was a distributed save loop in disguise, and the whole thing hinged on one decision: re-pin, don&apos;t navigate.</summary>
  </entry>
  <entry>
    <title>Why our agents don&apos;t get a laptop</title>
    <link href="https://good.vibes.diy/blog/agents-in-the-cloud.html"/>
    <id>https://good.vibes.diy/blog/agents-in-the-cloud.html</id>
    <updated>2026-06-28T12:00:00.000Z</updated>
    <published>2026-06-28T12:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>A capability that only works on a hand-configured laptop quietly pushes all the work back to the laptop. Here&apos;s why we made cloud containers the default home for agent QA — and three war stories from getting browser validation to run there.</summary>
  </entry>
  <entry>
    <title>Edit a stranger&apos;s app, and it&apos;s yours</title>
    <link href="https://good.vibes.diy/blog/the-vibe-owner-viewer-experience.html"/>
    <id>https://good.vibes.diy/blog/the-vibe-owner-viewer-experience.html</id>
    <updated>2026-06-28T11:00:00.000Z</updated>
    <published>2026-06-28T11:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>The /vibe page now meets you where you are: a non-owner edit forks the app to your handle in place, owners get a private draft they can publish in one tap, and small indicators always tell you whether you&apos;re the author, an admin, or a read-only guest.</summary>
  </entry>
  <entry>
    <title>We only needed one Durable Object</title>
    <link href="https://good.vibes.diy/blog/collapsing-durable-objects.html"/>
    <id>https://good.vibes.diy/blog/collapsing-durable-objects.html</id>
    <updated>2026-06-28T10:00:00.000Z</updated>
    <published>2026-06-28T10:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We had three Durable Object classes that were really one handler surface opened against three shard keys. Here&apos;s how we collapsed them into a single class — and which &apos;separate-class&apos; argument fell apart the moment we pushed on it.</summary>
  </entry>
  <entry>
    <title>We deleted our auth dependency. Nothing changed.</title>
    <link href="https://good.vibes.diy/blog/defireproofing-auth.html"/>
    <id>https://good.vibes.diy/blog/defireproofing-auth.html</id>
    <updated>2026-06-28T09:00:00.000Z</updated>
    <published>2026-06-28T09:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We moved our device-id PKI and Clerk token verifiers in-house, out of @fireproof/*, with zero call-site changes — gated by a byte-compatible golden harness so the lift was provably identical before we cut the dependency.</summary>
  </entry>
  <entry>
    <title>We deleted the preview pane</title>
    <link href="https://good.vibes.diy/blog/in-place-generation.html"/>
    <id>https://good.vibes.diy/blog/in-place-generation.html</id>
    <updated>2026-06-28T08:00:00.000Z</updated>
    <published>2026-06-28T08:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We moved first-generation onto the deployed app itself — stream into the card, hot-swap the running iframe, de-blur the app forming behind it — and in doing so deleted the separate preview pane entirely. The risk was the simplification.</summary>
  </entry>
  <entry>
    <title>Save a tree, skip the tests: leaner CI for docs-only PRs</title>
    <link href="https://good.vibes.diy/blog/save-a-tree-skip-the-tests.html"/>
    <id>https://good.vibes.diy/blog/save-a-tree-skip-the-tests.html</id>
    <updated>2026-06-28T06:30:00.000Z</updated>
    <published>2026-06-28T06:30:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>A README typo doesn&apos;t need a Playwright suite and a Postgres cluster. Teaching docs-only PRs to skip the heavy CI work — without falling into the &apos;required check stuck pending&apos; trap.</summary>
  </entry>
  <entry>
    <title>The NUL byte that broke every write (+7 more)</title>
    <link href="https://good.vibes.diy/blog/small-fixes-real-lessons.html"/>
    <id>https://good.vibes.diy/blog/small-fixes-real-lessons.html</id>
    <updated>2026-06-27T15:00:00.000Z</updated>
    <published>2026-06-27T15:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Eight little fixes from the build log — a NUL byte that took down every Postgres write, an iOS audio-unlock race, a markdown blank line that clobbered a file — each with a lesson bigger than the diff.</summary>
  </entry>
  <entry>
    <title>Teaching an AI you&apos;re not &apos;the owner&apos;</title>
    <link href="https://good.vibes.diy/blog/teaching-codegen-defaults.html"/>
    <id>https://good.vibes.diy/blog/teaching-codegen-defaults.html</id>
    <updated>2026-06-27T09:00:00.000Z</updated>
    <published>2026-06-27T09:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Generated apps used to default to owner-gated permissions — broken for everyone but the creator. Here&apos;s how we flipped the default to author-owned, steered the model toward multiplayer without ever saying &apos;don&apos;t,&apos; and built a metric so the prompt could iterate itself.</summary>
  </entry>
  <entry>
    <title>The vibe that locked out its owner</title>
    <link href="https://good.vibes.diy/blog/retiring-isowner.html"/>
    <id>https://good.vibes.diy/blog/retiring-isowner.html</id>
    <updated>2026-06-23T12:00:00.000Z</updated>
    <published>2026-06-23T12:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>A vibe locked its own owner out of saving. The fix wasn&apos;t a better isOwner check — it was deleting isOwner and treating &apos;owner&apos; as a seeded, revocable role instead of an ambient super-user.</summary>
  </entry>
  <entry>
    <title>How we batch-upgrade apps with screenshots</title>
    <link href="https://good.vibes.diy/blog/upgrading-apps-with-screenshots.html"/>
    <id>https://good.vibes.diy/blog/upgrading-apps-with-screenshots.html</id>
    <updated>2026-06-09T12:00:00.000Z</updated>
    <published>2026-06-09T12:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Every deployed Vibe serves both a live screenshot and its own source. That closes a visual feedback loop an agent can run alone — see the app, fix the code, push, look again — and fan out across dozens of apps at once.</summary>
  </entry>
  <entry>
    <title>How we eval the generator</title>
    <link href="https://good.vibes.diy/blog/how-we-eval-the-generator.html"/>
    <id>https://good.vibes.diy/blog/how-we-eval-the-generator.html</id>
    <updated>2026-06-09T11:00:00.000Z</updated>
    <published>2026-06-09T11:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>Every edit to the system prompt changes every app anyone generates. Here&apos;s the harness that measures generation quality — 46 prompts in three sets, scored 1–5, fanned out across a Workflow pipeline — so we know within a coffee break whether a change made things better or worse.</summary>
  </entry>
  <entry>
    <title>Can one English prompt rebuild our festival app?</title>
    <link href="https://good.vibes.diy/blog/can-a-prompt-rebuild-the-pickathon-app.html"/>
    <id>https://good.vibes.diy/blog/can-a-prompt-rebuild-the-pickathon-app.html</id>
    <updated>2026-06-09T10:00:00.000Z</updated>
    <published>2026-06-09T10:00:00.000Z</published>
    <author><name>Vibes DIY</name></author>
    <summary>We tried to recreate Pickathon&apos;s built-out 2026 app — data model, views, and a fiddly access policy — from a single plain-English prompt. It got ~90% there on description alone; a URL and a one-sentence schema closed the rest.</summary>
  </entry>
</feed>
