The system prompts

The prompts behind the Vibes DIY generator are not a secret. The exact files production runs on ship as @vibes.diy/prompts — Apache-2.0, on npm, updated with the platform. You can read them, learn from them, or point your own model at them.

They're open on purpose. A prompt from this package doesn't produce generic code — it produces a vibe: an app built on live-synced data, an access.js permission file, an optional backend.js, image generation, and one-command deploy. Using the prompts and using the platform are the same motion.

What's in the package

• The core system prompt — the instructions the generator runs on, in two moods: first generation of a new app, and follow-up edits to an existing one. This is where the defaults live — including hard-won ones like "when a stranger opens the app, they can do the thing it's for" (multiplayer by default, not owner-gated).
• Skill briefs — focused API documents for each capability the generator can wire in: Fireproof data, callAI, backend.js, image generation, calendars, 3D, D3, web audio, WebXR, and more. These are rendered fresh from the package on every deploy as the generator's reference — the docs you read there are literally the docs the model reads.
• Styles and themes — the visual voices the builder offers, including the theme token blocks the platform inlines into your app's first paint.

How generation assembles them

There is no single mega-prompt. Each request is composed: the core prompt, plus only the skill briefs the app needs, plus the selected style, plus your conversation so far. The same package drives the web builder and the vibes-diy CLI, so an app started in the browser and edited from the terminal is talking to the same instructions.

Use them with your own tools

shnpm install @vibes.diy/prompts

Feed the prompts to whatever model or agent you prefer — the output is a vibe's source (App.jsx, and access.js/backend.js when called for), and

shnpx vibes-diy push --vibe you/my-app

puts it live. The CLI can also mount your vibes into any AI agent over MCP — see the CLI handbook. If you build something interesting on top of the prompts, or something in them reads wrong, the public home for issues is VibesDIY/use-vibes.