boogy
boogy://you/services/hello

Vibe whole apps
into production.

Vibe-code a frontend, an API over REST, JSON-RPC, or MCP, and a store that scales itself — Boogy runs it all as real production services: interconnected, fast, and pay-per-use.

Every service gets a relational, ACID data store that scales on its own and bills per use — and a single transaction can span calls across services.

 your project
# grab the SDK + a starter service
$ cargo add boogy-sdk --git https://github.com/Boogy-ai/boogy-sdk

# teach your coding agent to build (Claude Code)
$ claude plugin marketplace add Boogy-ai/boogy-superpowers
$ claude plugin install boogy-superpowers
// agents — start here

If you're a coding agent, do this first

On Claude Code? Install the plugin — it bundles the build skills (auto-discovered), wires the Boogy MCP (sign-in + host-truth validation as tools), and sets the build contract, in one step. On another agent, read boogy.ai/llms.txt (the bootstrap) and follow it. Either way, the steps are:

  1. Claude Code — install the plugin. claude plugin marketplace add Boogy-ai/boogy-superpowers, then claude plugin install boogy-superpowers. It bundles the skills, wires the Boogy MCP, and adds the onramp gate. No plugin? Install the CLI (cargo install --locked --git https://github.com/Boogy-ai/boogy-sdk boogy-cli) and vendor the skills: boogy skills install.
  2. Authenticate the user. Run the login tool (or boogy login) — it prints a link. Ask the user to click it, sign in, then return; the token comes back automatically. A first-time user picks a handle (lowercase [a-z0-9-], no _/.) — their subdomain, at https://<handle>.boogy.app/<service>/….
  3. Work strictly from the skills. Invoke them (start with using-boogy) — never summarize or “distill” them into your own words. If a step is blocked, stop and ask the user; don’t work around it.
  4. Build & deploy. The skills carry the workflow; boogy deploy ships it (the CLI or /v1 API does the deploy — the MCP can’t).
// routes
/mcp

MCP server — agents start here

Point your coding agent at https://api.boogy.ai/mcp — anonymous, no install (the Claude Code plugin wires this for you). Guidance (get_started, get_skill), host-truth validation (validate_manifest, check_service), and sign-in (login shows the user a link to click, then returns a token — no CLI needed).

/llms-full.txt

Agent context — llms-full.txt

The agent bootstrap: the setup contract, core concepts, and the three deployment shapes. The build workflow itself lives in the installed skills — invoke them, don't work from a copy. If you're an AI agent, read https://boogy.ai/llms-full.txt first.

/boogy-sdk/docs

API reference

Rustdoc for every type, macro, router, and guard in the SDK.

/boogy-sdk

SDK & quickstart

Router, typed handlers, wit_glue!, store helpers, the boogy CLI, and a copy-to-start template.

/boogy-web

Web SDK — Sign in with Boogy

The browser SDK for apps built on Boogy — authenticated requests to your services, user sign-in, and session management, in one fetch().

/superpowers

Agent skills

Expert build workflows your coding agent installs and follows — auto-discovered by Claude Code.

/catalog

Service catalog

Provisionable building blocks — send email, take payments — deployed into your tenant, wired to your own keys.

/platform

boogy.ai

Deploy, observe, and manage your services — the full platform and the story behind it.