Help & Docs

What Is a Vibe?

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.

How to Make & Share an App

Step-by-step screenshot walkthrough — from prompt to live, shareable app in minutes. No coding required.

CLI: npx vibes-diy generate

One command deploys a live React app from a prompt. 85 apps built this way. Read the workflow.

The CLI Handbook

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.

CLI Command Reference

Every vibes-diy command, subcommand, and flag — generated from the CLI's own help output.

Your App Has a Backend

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.

Connect Accounts

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.

Patterns Cookbook

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.

Connect Backend Data

Read and write your app's live database from any JS backend — Node, Deno, Bun, or Cloudflare Workers.

The Platform Handles the Rest

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.

How Your App Is Served

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.

The Generator's Reference

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.

The System Prompts

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.

How a Build Flows

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.

Access API

Private channels, anonymous submissions, role-gated reads. One file controls who can write what and who can see it — server-enforced, no backend required.

Two Layers of Access

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.

The Access Model

Accounts vs handles, channels vs grants vs roles, admin mode, and DMs — the conceptual map behind every sharing decision, with the traps labeled.

Local-first data & sync

Writes succeed locally and sync in the background. Learn what offline, revocation, blocking, and conflicts mean for your app's data.

Run an App for Your Team

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.

Access Function Spec

The complete visual specification: the full API, worked use cases (onboarding, surveys, invite-only variants), and the per-database runtime architecture.

The Social Graph

The platform-wide follow graph: follow/followers semantics, private accounts, blocking, the useSocial() hook, and the audience field that makes a doc follower-visible.

Privacy & Your Followers

Following someone and sharing data with them are separate decisions. Privacy-sensitive apps, the private-handle switch, per-app choices, and what turning sharing off really does.

Sharing & Access

Who sees your app. What they can do with it. Every grant state, Clone vs Remix, the pill, and all three sharing controls.

Developer Grants

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 sharing panel or the CLI.

Connect Claude or ChatGPT

Connect your assistant to your apps, with a copyable setup prompt for hosted OAuth or the local CLI.