WELCOME TO FLAREBOT

a welcome! let's make your idea! — the comic

FLAREBOT flings open the workshop doors: LET'S MAKE YOUR IDEA!
A welcome! This repo is a workshop that comes with a robot. The trick is three rules: your keys live in .env (never committed), small scripts spend the keys, and Claude drives the scripts. You talk; the robot builds.
The Maker clones the repo while a crane lowers the robot skeleton onto the bench: STEP 1, FORK IT
Step 1 · Fork it Fork on GitHub, then point Claude Code at your fork — locally (git clone, then claude) or as a remote session on the web. The skeleton lands on your bench; the original stays untouched.
The Maker flips switches labeled DRAW, SHIP, RECAP, MAP while FLAREBOT presses TEST: STEP 2, THE WIZARD
Step 2 · The wizard Say “wizard” to Claude, or run python3 scripts/wizard.py and open http://127.0.0.1:8532. Every feature has an on/off switch; every key has a card.
The Maker feeds brass keys into FLAREBOT's .env hatch under a NEVER COMMIT KEYS stamp: STEP 3, YOUR KEYS
Step 3 · Your keys Paste keys into the wizard (it writes the gitignored .env) — each card shows what the key unlocks, a link to get a new one, and a Test button that probes the real API. Fill what you have; empty slots are fine. And obey the stamp.
DRAW ME A FOX! — Claude pulls the lever and FLAREBOT paints frames into a crate labeled art/: STEP 4, DRAW
Step 4 · Draw Ask for art in plain words — “draw me a fox piloting a hot-air balloon, three variations”. Claude crafts the prompt and runs scripts/genimg.sh; finished frames stack up in art/.
FLAREBOT catapults framed paintings up to a smiling cloud labeled workers.dev: STEP 5, SHIP
Step 5 · Ship “Ship it.” scripts/publish.sh builds a gallery page from art/ and deploys it to Cloudflare — your work goes live at <name>.workers.dev.
A corkboard with a RECAP calendar and a string-and-pins MAP graph, stamped LOCAL ONLY: STEP 6, LOOK INSIDE
Step 6 · Look inside Two instruments watch the workshop itself: “recap” draws a calendar of every work-day from git history, and “map the repo” pins up a nodes-and-edges graph where untested paths glow red — then Claude offers to write the missing tests. Both live in review/, gitignored: local only, never shipped.
The Maker bolts a NEW SCRIPT arm onto FLAREBOT beside a NEW KEY and a NEW SKILL blueprint: MAKE IT YOURS
Finale · Make it yours The skeleton is the starting point, not the product. Every new API you have a key for is a new arm for the robot — the recipe is below.
FLAREBOT and CLAUDE hoist the comic into a cloud castle labeled PAGES while the Maker cheers by a signpost reading ephemeral-sean.pages.dev: EPILOGUE, LIVE ON THE CLOUD
Epilogue · Live on the cloud And then it happened for real: this very comic — plus the calendar, the feature map, and its own source — was hoisted onto Cloudflare Pages at ephemeral-sean.pages.dev. The workshop published its own story.

How to extend this

Every capability in flarebot has the same four-part shape. Copy it and the whole kit — the wizard, the doctor, Claude's operator manual — picks your new power up:

  1. A script in scripts/ — bash + curl + python3 only, so it runs the same on a laptop and in a remote sandbox. It sources .env itself and fails loudly naming the key it wanted. (Look at scripts/genimg.sh — that's the template.)
  2. A key slot in .env.example — with a comment saying where to get the key. Add a matching entry to the KEYS list in scripts/wizard.py so it appears in the catalog with its own test button.
  3. A row in CLAUDE.md — the operator manual. One line in the tools table and Claude knows the new tool exists, what it costs, and when to reach for it.
  4. Optionally, a skill in .claude/skills/ — a short SKILL.md gives the capability a name you can say out loud (“draw”, “ship”, “transcribe”, “tweet”…) and a toggle in the wizard.

Then tell Claude to run “map the repo” again — your new arm shows up as nodes and edges, red until you test it.

NEVER COMMIT KEYS — .env is gitignored; if one ever leaks into a commit, rotate it at the provider. Deleting the commit is not enough.
review/ STAYS LOCAL — recap & map are instruments, not cargo. Publishing is always a deliberate copy into art/ + “ship it”.