← Index
The Bradbury Group

System Instructions

How we manage the prompts that power every AI surface

First Steps
1
Collect all instructions into a single Drive folder
Pull every current instruction set into one place. For each: capture the live text, confirm which platform it’s deployed on, and note the agent ID or URL. Target: Columbus, Solomon 1–4, Mr. Miyagi Gem, Course Tutor Gem, function library, ClickUp Super Agent, Walter, Claude.ai Projects.
Paige / Aperna
2
Resolve file format
YAML frontmatter is stripped by the sync script for ElevenLabs, but copy/paste platforms (Gemini Gems, Claude.ai Projects, ClickUp) ingest it as noise.
Decide: keep YAML, strip to clean Markdown, or use sidecar metadata.
Charlie
3
Load into repo in standard format
Once format is settled, convert all collected instructions and commit. Solomon 3 & 4 source files already in SuperAssistant repo — mechanical conversion. Everything else comes from step 1 collection.
Charlie

The Problem

  • Instructions scattered across Drive, repos, and platform UIs
  • No one knows which version is current
  • No record of what changed, when, or why
  • Gemini Gems pasted twice — .com and .net — with no sync
  • Same prompts live in 3+ places with no connection

The Fix

  • One GitHub repo — single source of truth for every prompt
  • Full version history on every change
  • Auto-deploy where APIs exist, clear process where they don’t
  • Team notified on every update with diff and action required
  • Same format everywhere — YAML + Markdown
Today

Google Drive

Stale since June 2025. No version history.

App Repos

TSE-stripped, SuperAssistant, Walter. Each has its own copy.

Platform UIs

Pasted into ElevenLabs, Gemini, ClickUp. No record.

6 platforms, 6 different update methods, zero visibility.
↓
Target

GitHub

Single source of truth. Every system prompt in one place. Full history, reviewable, deployable.

Infrastructure needed & cost

S
Supabase Storage
Runtime fetch bucket. Backend pulls latest instructions on each call.
$0 — included in existing Supabase plan
A
GitHub Actions
CI/CD. Runs validation and sync scripts on push. sync-elevenlabs.yml, validate.yml.
$0 — free for public repos
R
Railway
Hosts Walter and SuperAssistant backends.
$0 — already running, no change
K
ElevenLabs API key
One secret in repo settings. Enables auto-deploy to live voice agents.
$0 — key already exists in TSE-stripped
T
ClickUp task
Committer creates task for updater with file link and diff. Already part of daily workflow.
$0 — already using ClickUp
H
Webhook handler
Thin service for ClickUp runtime fetch. Same pointer pattern as ElevenLabs.
$0 — Supabase Edge Function, free tier covers it
Push once, deploy everywhere
A
ElevenLabs
Auto · Charlie
Git push updates live voice agents via API.
A
Claude API
Auto · Charlie
Backend fetches latest from Supabase on deploy.
A
Claude Code
Auto · Charlie
CLAUDE.md files live in repo. Pull to update.
A
Gemini API
Auto · Charlie
system_instruction param fetches from Supabase.
Push notifies, human applies
M
Gemini Gems App
Manual · Aperna
Copy once, paste into .com and .net. ClickUp task prompts the step.
M
Claude.ai Projects
Manual · Charlie / Paige
Paste into project custom instructions. History in GitHub.
M
ClickUp AI
Manual · Paige
Static pointer in UI. Runtime instructions via webhook.
The bottom line: One repo. One format. Everyone knows where to look and what changed. Auto where we can, clear process where we can’t. No more hunting through Drive folders or guessing which version is live.
The-Bradbury-Group/tbg-system-instructions · June 2026