Journey Templates

This is the final, optional stop in the Butterbase journey workflow. It walks you through turning your deployed app into a cloneable public template: writing a proper README that explains every manual setup step (OAuth, agents, MCP servers, secrets), bundling agent spec files, dry-running the snapshot push to catch stray secrets, flipping visibility to public, and self-clone testing in a scratch directory to prove the instructions actually work. The honest take: most projects should skip this. It's skipped by default in hackathon mode for good reason. Only run it if you genuinely want strangers to fork your app, and even then, budget time for the README. A half-done template is worse than no template.

GitHub stars: 532
last updated: Jun 11, 2026

View on GitHub

Install

$ npx -y skills add butterbase-ai/butterbase-skills --skill journey-templates --agent claude-code

Installs into .claude/skills of the current project.

Files

Journey: Publish-as-template (optional)

Turn the deployed app into a public, forkable template. This stage is only for apps the user explicitly wants to share — most journeys end at deploy (or submit in hackathon mode).

When to use

Dispatched by journey when current_stage: templates.
Directly via /butterbase-skills:journey-templates.
The row is optional in the checklist; skip silently if the user declines.

Inputs

A deployed, working app (post-journey-deploy).
docs/butterbase/02-plan.md — to know what features the app uses (agents, MCP servers, OAuth providers, function env vars).
docs/butterbase/04-build-log.md — to confirm deploy smoke passed.

Preflight

00-state.md must have current_stage: templates or later AND deploy ticked.
The @butterbase/cli must be installed locally (butterbase --version works). If not, invoke journey-preflight to fix.
The repo must be bound: .butterbase/config.json exists with the right currentApp. If not, run butterbase repo init <app_id>.