A skill your agent uses 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.

MITAuto-check passed

Install Journey

skills CLI
$ npx skills add butterbase-ai/butterbase-skills --skill journey -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install butterbase-ai/butterbase-skills journey --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/journey .claude/skills/journey && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
journey
GitHub stars
534
Token cost
~1.8k tokens
SKILL.md length
744 words
Files
1
Skills in repo
39
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses 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.

  • Works in 3 steps: Detect state. Check whether… → Confirm with user. Print a one-line… → Dispatch. Invoke the matching skill via…
  • The user says build an app
  • SKILL.md covers When to use, Toolchain, Procedure and Starter 00-state.md template, plus 2 more sections
  • Calls npm

What it does

Journey is an agent skill from butterbase-ai/butterbase-skills. 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.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Plugin for Butterbase.ai. The licence is MIT.

When your agent uses it

  • The user says build an app
  • I have an idea for
  • Otherwise signals they want to go from idea to deployed Butterbase app

Example prompts

  • “build an app”
  • “s start”
  • “help me build”
  • “/journey”

Requirements

  • Node.js

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Detect state. Check whether docs/butterbase/00-state.md exists in the working directory.
  2. Confirm with user. Print a one-line summary of where we are: "Resuming journey at for app_id ." Ask: "Continue from ? (yes / jump to other…
  3. Dispatch. Invoke the matching skill via the Skill tool. Do not do the stage's work inline — delegate.

What it can do on your machine

Read from SKILL.md and the folder at commit aa8ae69. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Journey loads about 1.8k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 744 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~94
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from butterbase-ai/butterbase-skills at commit aa8ae69, republished under its MIT licence (© butterbase-ai). 744 words, ~1,778 tokens.

Download SKILL.mdSave it as .claude/skills/journey/SKILL.md (or your agent's skills folder).
name
journey
description
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.

Butterbase Guided Journey

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.

When to use

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.

Toolchain

The journey assumes two npm packages alongside the MCP tools:

PackageRoleWhen to install
@butterbase/sdkTypeScript 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/cliLocal-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.

Procedure

  1. Detect state. Check whether docs/butterbase/00-state.md exists in the working directory.

    • If absent: this is a fresh journey. Ask the user "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.
    • If present: read the front-matter and the stage checklist. Identify the first unchecked, non-skipped stage. That is the next stage.
  2. 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)".

  3. Dispatch. Invoke the matching skill via the Skill tool. Do not do the stage's work inline — delegate.

    StageSkill
    ideabutterbase-skills:journey-idea
    planbutterbase-skills:journey-plan
    preflightbutterbase-skills:journey-preflight
    docsbutterbase-skills:journey-docs
    schemabutterbase-skills:journey-schema
    rlsbutterbase-skills:journey-rls
    authbutterbase-skills:journey-auth
    storagebutterbase-skills:journey-storage
    functionsbutterbase-skills:journey-functions
    aibutterbase-skills:journey-ai
    ragbutterbase-skills:journey-rag
    realtimebutterbase-skills:journey-realtime
    durablebutterbase-skills:journey-durable
    agentsbutterbase-skills:journey-agents
    frontendbutterbase-skills:journey-frontend
    deploybutterbase-skills:journey-deploy
    substratebutterbase-skills:journey-substrate (optional)
    submitbutterbase-skills:journey-submit (hackathon_mode only)
    templatesbutterbase-skills:journey-templates (optional)

Docs gate. Stage docs runs once, right after preflight, to prime butterbase_docs for every capability in the plan. Subsequent build stages start with the relevant docs cached at docs/butterbase/03b-docs-cache.md. If the user changes the plan mid-build, re-run /butterbase-skills:journey-docs before the affected stage.

Show full SKILL.md (266 more words)Show less
  1. After the stage skill returns, re-read 00-state.md and ask the user whether to advance to the next unchecked stage. Stage selection rules:
    • Build-stage order is: schema → rls → auth → storage → functions → ai → rag → realtime → durable → agents → frontend.
    • If hackathon_mode: true and all build stages are done, the next stage is deploy then substrate then submit then templates.
    • If hackathon_mode: false, the journey ends at deploy unless the user opts into templates — skip substrate and submit entirely (treat them as (n/a)).
    • The substrate stage is always optional. In hackathon mode, default to skipping it (mark as (n/a — optional, can add post-submission)); in non-hackathon mode, skip it entirely as it is not part of the core journey.
    • The templates stage is always optional. It runs after deploy (non-hackathon) or after submit (hackathon). Default is to skip unless 01-idea.md or 02-plan.md flags publish_as_template: true.
    • Loop until the cursor reaches DONE (every stage checked or annotated n/a).

Starter 00-state.md template

When initialising a fresh journey, write this to docs/butterbase/00-state.md (ask the user "Is this a hackathon submission? (yes/no)" first to set hackathon_mode):

markdown
---
app_id: null
api_base: null
hackathon_mode: <true|false>
hackathon_deadline: null
frontend_stack: null
current_stage: idea
last_updated: <ISO-8601 timestamp>
---

# Journey state

## Stages
- [ ] idea
- [ ] plan
- [ ] preflight
- [ ] docs
- [ ] schema
- [ ] rls
- [ ] auth
- [ ] storage
- [ ] functions
- [ ] ai
- [ ] rag
- [ ] realtime
- [ ] durable
- [ ] agents
- [ ] frontend
- [ ] deploy
- [ ] substrate (optional)
- [ ] submit
- [ ] templates (optional)

## Notes
- Journey initialised <ISO date>.

If hackathon_mode: false, write the submit row as - [ ] submit (n/a — not a hackathon) instead of the plain unchecked form, so the orchestrator and any direct stage invocation will skip it.

Outputs

  • Creates docs/butterbase/ and 00-state.md on first run.
  • Updates current_stage and last_updated in 00-state.md whenever it dispatches.

Anti-patterns

  • ❌ Doing a stage's work inline instead of delegating to its skill. The orchestrator only routes.
  • ❌ Skipping the "Continue from <stage>?" confirmation — users may want to jump or redo.
  • ❌ Letting 00-state.md drift out of sync. Always re-read after each stage returns.

© butterbase-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/journey of butterbase-ai/butterbase-skills.

Open the folder on GitHubat commit aa8ae69

Compare with similar skills

Journey next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Journey compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Journey this skillbutterbase-ai/butterbase-skills534—~1.8kAutomated safety check: PassMIT
Const Letthedaviddias/Front-End-Checklist74k—~469Automated safety check: PassMIT
Customer Journey Mapphuryn/pm-skills27k—~816Automated safety check: PassMIT
Customer Journey Map Builderdeanpeters/Product-Manager-Skills7.2k1 repos~3.7kAutomated safety check: PassCustom licence
Android UI Journey Testingsickn33/agentic-awesome-skills47k1 repos~1.9kAutomated safety check: PassMIT
Customer Journey Mapping Workshopdeanpeters/Product-Manager-Skills7.2k1 repos~4.7kAutomated safety check: PassCustom licence

Similar skills

  • Const Let

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Prefer const and let over var.

    74k GitHub stars~469 tokensUpdated 4 days ago
    Auto-check passed
  • Customer Journey Map

    phuryn/pm-skills

    Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities.

    27k GitHub stars~816 tokensUpdated yesterday
    Product & Project ManagementAuto-check passed
  • Customer Journey Map Builder

    deanpeters/Product-Manager-Skills

    Builds a stage-by-stage customer journey map covering actions, touchpoints, emotions, KPIs, goals, and owning teams for one persona and scenario.

    7.2k GitHub starsUsed in 1 repo~3.7k tokens
    Product & Project ManagementAuto-check passed
  • Android UI Journey Testing

    sickn33/agentic-awesome-skills

    XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.

    47k GitHub starsUsed in 1 repo~1.9k tokens
    MobileAuto-check passed
  • Customer Journey Mapping Workshop

    deanpeters/Product-Manager-Skills

    Walks a product manager through a customer journey map one question at a time, from persona and scenario to pain points and opportunities.

    7.2k GitHub starsUsed in 1 repo~4.7k tokens
    Product & Project ManagementAuto-check passed
  • User Journey Mapper

    jeremylongshore/tons-of-skills-marketplace

    Manage user journey mapper operations. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~558 tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

More from butterbase-ai/butterbase-skills

All 39 skills in this repo
  • AI

    butterbase-ai/butterbase-skills

    A skill your agent uses when calling the app's AI gateway from agent tools — chat completions, embeddings, listing models, configuring defaults or BYOK, reading token/cost usage

    534 GitHub stars~1.1k tokensUpdated 5 days ago
    Auto-check passed
  • Auth Setup

    butterbase-ai/butterbase-skills

    A skill your agent uses when configuring OAuth providers (Google/GitHub/Apple/X/etc.), setting up post-login auth hooks, tuning JWT lifetimes, or generating service API keys

    534 GitHub stars~2.2k tokensUpdated 5 days ago
    Auto-check passed
  • Build App

    butterbase-ai/butterbase-skills

    A skill your agent uses when building a new Butterbase app from scratch, creating a full-stack application, or when the user asks to set up a complete backend with database, auth, and deployment

    534 GitHub stars~4.9k tokensUpdated 5 days ago
    Auto-check passed
  • Contributing

    butterbase-ai/butterbase-skills

    A skill your agent uses when contributing to the Butterbase codebase, adding new MCP tools, creating API routes, writing migrations, or understanding the monorepo architecture

    534 GitHub stars~1.5k tokensUpdated 5 days ago
    Auto-check passed
  • Debug Rls

    butterbase-ai/butterbase-skills

    A skill your agent uses when users report access denied errors, see wrong data, RLS policies are not working, or when troubleshooting Row-Level Security issues in Butterbase

    534 GitHub stars~3.5k tokensUpdated 5 days ago
    Auto-check passed
  • Deploy Frontend

    butterbase-ai/butterbase-skills

    A skill your agent uses when deploying a frontend (React, Next.js, or static HTML) to a live URL on Butterbase, or when troubleshooting deployment issues like MIME type errors or blank pages

    534 GitHub stars~2.8k tokensUpdated 5 days ago
    Auto-check passed

Questions about Journey

What does Journey do?

A skill your agent uses 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. Journey is an agent skill from butterbase-ai/butterbase-skills. 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.

When should I use Journey?

Journey fits situations like: the user says build an app; I have an idea for; otherwise signals they want to go from idea to deployed Butterbase app.

How do I install Journey in Claude Code?

Run `npx skills add butterbase-ai/butterbase-skills --skill journey -a claude-code`. Or copy the skill folder (skills/journey in butterbase-ai/butterbase-skills) into .claude/skills/journey in your project. Claude Code loads it when a task matches its description.

How do I install Journey in Codex?

Run `npx skills add butterbase-ai/butterbase-skills --skill journey -a codex`. Or copy the skill folder (skills/journey in butterbase-ai/butterbase-skills) into .agents/skills/journey in your project. Codex loads it when a task matches its description.

Can I use Journey in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add butterbase-ai/butterbase-skills --skill journey -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/journey, .gemini/skills/journey, .github/skills/journey and .opencode/skills/journey in your project.

What does Journey need to run?

Going by SKILL.md and its folder, Journey needs the command-line tools its instructions call (npm). Our summary lists: Node.js.

Does Journey access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Journey safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Journey use?

Journey is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Journey use?

About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Journey?

Skills that share tags, products or a category with Journey: Const Let (thedaviddias/Front-End-Checklist, 74k stars), Customer Journey Map (phuryn/pm-skills, 27k stars), Customer Journey Map Builder (deanpeters/Product-Manager-Skills, 7.2k stars) and Android UI Journey Testing (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Journey?

butterbase-ai (a GitHub organization) maintains it in butterbase-ai/butterbase-skills, which has 534 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 5, 2026.

Source: butterbase-ai/butterbase-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.