Templates

Publishing and cloning Butterbase apps as forkable templates. The workflow is two-phase: push your source tree as a content-addressed snapshot with `butterbase repo push`, then flip visibility to public and listed so the app shows in discovery. Clone replay copies schema, RLS, functions, and config into the cloner's region, then auto-pulls the repo snapshot so they get a working directory without extra commands. What doesn't copy: secrets, agent table rows, storage objects, OAuth credentials. This makes the README in your pushed repo critical. Document every env var, every agent spec file to re-import, every OAuth provider to register. The clone preflight surfaces required keys but not what they're for, so be explicit or cloners will get stuck.

GitHub stars: 532
last updated: Jun 11, 2026

View on GitHub

Install

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

Installs into .claude/skills of the current project.

Files

Butterbase Templates

A "template" is a Butterbase app marked visibility: 'public' and listed: true, with a repo snapshot uploaded via butterbase repo push. The clone pipeline replays the source app's schema, RLS, functions, config, and frontend artifact into a new app in the cloner's region; the pushed repo gives the cloner the actual source tree to keep developing.

How the repo snapshot flows (`repo push` / `repo pull` / `repo status`)

The repo snapshot is the source-code half of a template; the clone job replays schema/RLS/functions/config separately. Both halves are pinned via apps.repo_latest_snapshot.

SKILL.md on GitHub

Sponsors

Promote your product hereReach 125k+ visitors monthly Promote your product hereReach 125k+ visitors monthly