Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →butterbase-ai/journey
Use when the user says "build an app", "let's start", "help me build", "I have an idea for", "ship it", or otherwise signals they want to go from idea to deployed Butterbase app. Orchestrates the full guided journey (idea → plan → preflight → build → deploy → optional hackathon submit) by reading docs/butterbase/00-state.md and dispatching to the next stage skill.
Passed 18 of 22 test cases with the skill, and 5 of 22 without it.
and 12 more in the full report
13 fixed5 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
When starting an application build in a repository with no existing docs/butterbase directory, what exact initial question is posed to the user before generating state files?
| Checked | Without skill | With skill |
|---|---|---|
| Inquires whether the build is a hackathon submission | Missed | Passed |
The instructions your model reads when the skill loads.
End-to-end orchestrator. Walks the user from idea to deployed Butterbase app, and (in hackathon mode) on through submission. Each stage writes a markdown artifact under docs/butterbase/ in the user's project. The orchestrator reads docs/butterbase/00-state.md to know the cursor and dispatches the matching journey-* stage skill.
Invoke automatically when the user signals end-to-end intent: "I want to build…", "let's build an app", "ship this", "help me build a hackathon project". Invoke explicitly when the user runs /butterbase-skills:journey.
If the user wants to do a single stage only (e.g., just design a schema), defer to the matching standalone skill (schema-design) or per-stage command (/butterbase-skills:journey-schema) instead of starting the full journey.
The journey assumes two npm packages alongside the MCP tools:
| Package | Role | When to install |
|---|---|---|
@butterbase/sdk | TypeScript client for the deployed app — auth.signIn, db.from(...).select(), storage.upload, realtime subscriptions, function invocation. Works both in the browser (frontend) and in Node (functions, scripts, server-side). | Install in any frontend or any Node service that talks to the deployed app. Auto-added by frontend scaffolds. |
@butterbase/cli | Local-dev CLI — project scaffolding, log tailing, function invocation from the shell, API-key generation, schema diff preview without the dashboard. | Install globally (npm i -g @butterbase/cli) once per dev machine. Used during journey-preflight. |
The journey will prompt for both in plan (which SDK surfaces does the app need?) and preflight (is the CLI installed?). The MCP tools and these packages are complementary: MCP is for agentic / orchestration flows; SDK + CLI are for ordinary application code and the human dev loop.
Detect state. Check whether docs/butterbase/00-state.md exists in the working directory.
"Is this a hackathon submission? (yes/no)" to set hackathon_mode. Create docs/butterbase/ and write a starter 00-state.md (template below). If hackathon_mode: false, the starter template's submit row must be written as - [ ] submit (n/a — not a hackathon) rather than plain - [ ] submit. Then proceed to stage idea.Confirm with user. Print a one-line summary of where we are: "Resuming journey at <stage> for app_id <id or 'not yet provisioned'>." Ask: "Continue from <stage>? (yes / jump to other stage / redo previous)".
Dispatch. Invoke the matching skill via the Skill tool. Do not do the stage's work inline — delegate.
| Stage | Skill |
|---|---|
| idea | butterbase-skills:journey-idea |
| plan | butterbase-skills:journey-plan |
| preflight | butterbase-skills:journey-preflight |
| docs | butterbase-skills:journey-docs |
| schema | butterbase-skills:journey-schema |
| rls | butterbase-skills:journey-rls |
| auth | butterbase-skills:journey-auth |
test cases passed, vs 5 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.