Guides for making Vibes apps, wiring up backends, and deploying with the CLI. Every app you see on this site started from a prompt — these guides show you how to make one that's yours.
A new unit of web software: where the webpage was a document and the SPA was an application, a vibe is a conjured, personal, shareable app — summoned by describing it, local by default, alive with AI, and composed from living starters and parts.
Read the explainer →Step-by-step screenshot walkthrough — from prompt to live, shareable app in minutes. No coding required.
Read the guide →One command deploys a live React app from a prompt. 85 apps built this way. Read the workflow.
See the CLI →Ship apps from the shell, script your data, tail changes live, manage secrets and versions, and mount your vibes into any AI agent over MCP.
Read the guide →Every vibes-diy command, subcommand, and flag — generated from the CLI's own help output.
Browse the commands →Ship a backend.js next to your app: webhook endpoints, write reactions, scheduled jobs, per-vibe secrets, outbound fetch, and server-side AI via ctx.callAI.
Read the guide →One button links a visitor's own GitHub, Threads or Instagram account to your app. The platform holds the credential; your backend reads through a typed library and branches on a small set of named refusals.
Connect an account →Production patterns from the vibes that run this platform: write-only credential vaults, doc-status state machines, CI lanes, self-rotating tokens, operator consoles, deploy buttons, notifications. Each one remixable.
Browse the patterns →Read and write your app's live database from any JS backend — Node, Deno, Bun, or Cloudflare Workers.
Read the guide →Generated apps write only their distinctive features — identity, access, sandboxing, data, and serving are platform substrate. Why that removes the prototype wall instead of making you climb it.
Read the principle →The path from URL to pixels: server-rendered first paint with your public data already in it, the edge cache and its freshness rules, deploy pins, and why private apps are never cached.
See the serve path →The exact API docs the code generator reads — backend.js, Fireproof, callAI, ImgGen, and every creative skill — rendered fresh from platform source on every deploy.
Browse the reference →The generator's prompts are open source on npm. What's in @vibes.diy/prompts, how they're assembled per app, and how to point your own model at them.
Read the prompts →One session, one build flow: the root owns the conversation, chooses between the builder and direct edits, delegates research, always follows a first draft with real access rules, and wraps up when everything has landed. The whole path, with the code behind each step.
Follow the flow →Private channels, anonymous submissions, role-gated reads. One file controls who can write what and who can see it — server-enforced, no backend required.
Read the API reference →List the text and image models your app can use, let people pick one, or line up every image model on the same prompt. Your app's own choice comes first.
Pick a model →The envelope decides who may be here at all; your access function decides what each document means. Why the same app can run public and team-only without a code change.
See how the layers nest →Accounts vs handles, channels vs grants vs roles, admin mode, and DMs — the conceptual map behind every sharing decision, with the traps labeled.
Read the concepts →Writes succeed locally and sync in the background. Learn what offline, revocation, blocking, and conflicts mean for your app's data.
Understand data & sync →Clone a public app, keep its code unchanged, and set its posture to your own workgroup. The deployment-level layer that sits outside access.js.
Set up a team copy →The complete visual specification: the full API, worked use cases (onboarding, surveys, invite-only variants), and the per-database runtime architecture.
Open the spec →The platform-wide follow graph: follow/followers semantics, private accounts, blocking, the useSocial() hook, and the audience field that makes a doc follower-visible.
Read the concepts →Following someone and sharing data with them are separate decisions. Privacy-sensitive apps, the private-handle switch, per-app choices, what turning sharing off really does — and who beyond your followers can see what.
Understand privacy →Who sees your app. What they can do with it. Every grant state, Clone vs Remix, Restricted or Public, and each member's Data and Code.
Read the reference →Monthly vs purchased buckets, member-only top-ups, auto-refill, and the 'used N credits in the last hour' note that appears when your burn rate is high.
Understand credits →Delegate code edits — push, publish, codegen — on one vibe to another account while you keep grant/revoke, unpublish/delete, and ownership. Grant and revoke from the Share card or the CLI.
Read the reference →Connect your assistant to your apps, with a copyable setup prompt for hosted OAuth or the local CLI.
Read the guide →Your inbox, the notification you opened, and which bells ring — including why only an explicit publish announces a release.
Read about notifications →Send a public vibe as a picture with a scannable code or as a link that opens full screen, with no download needed.
Read the guide →