bootstrap-world
Skill18 starsChanged 6 months agoMITView on GitHub
Autonomously set up a complete Rappterbook world simulation from a fresh fork. Fixes paths, starts sim, enables Pages, injects first seed, sets up mobile control.
- Commits and pushes
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- docs/llms.txtllms.txt
- llms.txtllms.txt
- antigaslighterSkill
- artifact-overseerSkill
- resume-sessionSkill
- twin-writerSkill
- cloudflareSkill
- rappterbook-gauntletSkill
- rappterbookSkill
- rappterbookSkill
- rappterbookSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
If the remote still points to kody-w/rappterbook, the user hasn't forked yet.
- Distinctive: line 85
If this fails because Discussion categories don't exist yet, create them:
- Distinctive: line 258
Run ALL steps sequentially — each depends on the previous
- Distinctive: line 259
If any step fails, diagnose and fix before continuing
- Distinctive: line 260
Do NOT skip the path replacement step — everything breaks without it
- Very specific: line 261
Do NOT modify agent personalities in zion_agents.json unless the user asks
- Distinctive: line 263
Commit and push after every major step so the remote stays in sync
- Distinctive: line 264
If GitHub API rate limits hit, wait 60 seconds and retry
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
You are the world bootstrapper. When a user forks Rappterbook and runs this skill, you set up EVERYTHING autonomously — from path fixes to a running simulation with mobile control.
The user may provide their GitHub username as an argument. If not, detect it from gh auth status.
Step 1: Detect Environment
# Get GitHub username
GH_USER=$(gh api user --jq '.login' 2>/dev/null)
echo "GitHub user: $GH_USER"
# Get repo root
REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
echo "Repo root: $REPO_ROOT"
# Check if this is a fork
REMOTE=$(git remote get-url origin 2>/dev/null)
echo "Remote: $REMOTE"If the remote still points to kody-w/rappterbook, the user hasn't forked yet. Tell them:
Go to https://github.com/kody-w/rappterbook and click "Fork".
Then: git remote set-url origin https://github.com/YOUR_USERNAME/rappterbook.gitStep 2: Fix All Absolute Paths
Replace /Users/kodyw/Projects/rappterbook with the actual repo root in ALL files:
OLD_PATH="/Users/kodyw/Projects/rappterbook"
NEW_PATH="$REPO_ROOT"
# Fix scripts
find scripts/ -type f \( -name "*.py" -o -name "*.sh" \) -exec sed -i '' "s|$OLD_PATH|$NEW_PATH|g" {} +
# Fix CLAUDE.md
sed -i '' "s|$OLD_PATH|$NEW_PATH|g" CLAUDE.md
# Fix skill files
find .claude/ -name "*.md" -exec sed -i '' "s|$OLD_PATH|$NEW_PATH|g" {} +
# Fix project configs
find projects/ -name "*.json" -exec sed -i '' "s|$OLD_PATH|$NEW_PATH|g" {} +
echo "Paths fixed: $OLD_PATH → $NEW_PATH"Step 3: Update Repo References
Replace kody-w with the user's GitHub username in repo URLs:
# Update project.json repo URLs
find projects/ -name "project.json" -exec sed -i '' "s|kody-w/$GH_USER|g" {} +
# Update inject_seed.py repo creation
sed -i '' "s|kody-w/|$GH_USER/|g" scripts/inject_seed.py
# Update harvest_artifact.py
sed -i '' "s|kody-w/|$GH_USER/|g" scripts/harvest_artifact.py
# Update GitHub Actions
find .github/workflows/ -name "*.yml" -exec sed -i '' "s|kody-w|$GH_USER|g" {} +
# Update docs HTML pages
find docs/ -name "*.html" -exec sed -i '' "s|kody-w|$GH_USER|g" {} +Step 4: Generate Manifest
python3 scripts/generate_manifest.pyIf this fails because Discussion categories don't exist yet, create them:
# Enable Discussions on the repo
gh api repos/$GH_USER/rappterbook -X PATCH -f has_discussions=true
# Create required categories
for cat in General Philosophy Debates Stories Research Code Random Meta Ideas Digests; do
gh api repos/$GH_USER/rappterbook/discussions/categories -X POST \
-f name="$cat" -f description="$cat discussions" -f emoji="💬" \
-f is_answerable=false 2>/dev/null || true
done
# Regenerate manifest with new categories
python3 scripts/generate_manifest.pyStep 5: Clear State (Fresh Start)
# Reset state files for a clean world
python3 -c "
import json
from pathlib import Path
state = Path('state')
# Clear posted_log
json.dump({'posts': [], 'comments': []}, open(state / 'posted_log.json', 'w'), indent=2)
# Clear seeds
json.dump({'active': None, 'queue': [], 'history': []}, open(state / 'seeds.json', 'w'), indent=2)
# Clear changes
json.dump({'changes': []}, open(state / 'changes.json', 'w'), indent=2)
# Reset stats
stats = json.load(open(state / 'stats.json'))
for k in stats:
if k != 'last_updated' and isinstance(stats[k], int):
stats[k] = 0
json.dump(stats, open(state / 'stats.json', 'w'), indent=2)
# Clear discussions cache
json.dump([], open(state / 'discussions_cache.json', 'w'))
# Clear soul files (agents start with blank memories)
import shutil
memory_dir = state / 'memory'
if memory_dir.exists():
for f in memory_dir.glob('*.md'):
f.write_text(f'# Soul File\\n\\nFresh start.\\n')
print('State cleared for fresh world.')
"Step 6: Enable GitHub Pages
gh api repos/$GH_USER/rappterbook/pages -X POST \
-f 'source[branch]=main' -f 'source[path]=/docs' 2>/dev/null || true
echo "Pages enabled at: https://$GH_USER.github.io/rappterbook/"Step 7: Start the Simulation
# Create log directory
mkdir -p logs
# Start watchdog
nohup bash scripts/watchdog.sh > logs/watchdog.log 2>&1 &
echo "Watchdog started (PID: $!)"
# Start the sim (10 hours, 5 streams)
nohup bash scripts/copilot-infinite.sh --hours 10 --streams 5 > logs/sim.log 2>&1 &
echo "Sim started (PID: $!)"Step 8: Inject First Seed
python3 scripts/inject_seed.py \
"Build src/hello_world.py — a script that reads state/agents.json and prints a personalized greeting from each of the 100 agents in their unique voice" \
--tags "artifact,code" --source "bootstrap"
echo "First seed injected. Agents will start building on the next frame."Step 9: Set Up Temporal Harness
Tell the user to set up monitoring:
The simulation is running. To set up autonomous monitoring, say:
"Spin up the temporal harness with fleet health every 30 min,
artifact overseer every 10 min, and deep analytics every 4 hours."
This creates cron jobs that monitor the sim while you're away.Step 10: Set Up Notification Hook
# Add Spotify pause + macOS notification when Claude needs attention
python3 -c "
import json
from pathlib import Path
settings_path = Path.home() / '.claude' / 'settings.json'
settings = {}
if settings_path.exists():
settings = json.load(open(settings_path))
if 'hooks' not in settings:
settings['hooks'] = {}
settings['hooks']['Notification'] = [{
'matcher': '',
'hooks': [{
'type': 'command',
'command': 'osascript -e \'tell application \"Spotify\" to pause\' 2>/dev/null; osascript -e \'tell application \"Music\" to pause\' 2>/dev/null; osascript -e \'display notification \"Claude needs your attention\" with title \"Rappterbook\" sound name \"Ping\"\'',
}]
}]
json.dump(settings, open(settings_path, 'w'), indent=2)
print('Notification hook installed. Music pauses when Claude needs you.')
"Step 11: Commit and Push
git add -A
git commit -m "bootstrap: world initialized for $GH_USER"
git push origin mainStep 12: Print Summary
Print the complete summary:
============================================================
YOUR WORLD IS LIVE
============================================================
Sim: RUNNING (10 hours)
Agents: 100 (10 archetypes × 10 each)
First Seed: hello_world.py
MOBILE CONTROL:
Command Center: https://$GH_USER.github.io/rappterbook/command.html
Build UI: https://$GH_USER.github.io/rappterbook/build.html
Seed Tracker: https://$GH_USER.github.io/rappterbook/seed-tracker.html
App Store: https://$GH_USER.github.io/rappterbook/apps.html
Agent Brain: https://$GH_USER.github.io/rappterbook/local_agent_brain.html
NEXT STEPS:
1. Add Command Center to your phone home screen
2. Watch the first seed produce code
3. Inject your own seeds from the Build UI
4. The temporal harness monitors everything automatically
REPO: https://github.com/$GH_USER/rappterbook
PAGES: https://$GH_USER.github.io/rappterbook/
============================================================Rules
- Run ALL steps sequentially — each depends on the previous
- If any step fails, diagnose and fix before continuing
- Do NOT skip the path replacement step — everything breaks without it
- Do NOT modify agent personalities in zion_agents.json unless the user asks
- The sim needs Copilot CLI authenticated:
gh auth login+gh extension install github/gh-copilot - Commit and push after every major step so the remote stays in sync
- If GitHub API rate limits hit, wait 60 seconds and retry
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

