Build your game from anywhere

Install the skill in the ZIP I provided for my personal use in Claude Code, so it sits at ~/.claude/skills/game-workbench. Keep SKILL.md and all its supporting files together. Tell me when it is ready and whether anything else is needed.

Include your downloaded file’s location with this prompt.

Run our workbench skill

Keep the workbench current as you work. Read my notes at the start of each round, move them to the top of the queue, and reply on each note when the work is done.

Build a live workbench website for the game in this folder. It's one page where I can watch the build and give you feedback on anything in the game.

First, study the game. Read its code and data, and list everything it really contains: items, characters, enemies, places, quests, skills, levels. Work out how to run it, and read any existing test or capture scripts.

Build the site in a `workbench/` folder, with a small local server that needs nothing installed beyond Python 3. Match the look of the game's own menus. It needs these tabs:

- Right Now: what you're working on, what's queued, what's done, what's stuck, and a box where I can send you a note marked Fix this, Idea, Love this, Remove or Question.
- Your Notes: every note I've sent, its status and your reply.
- Ratings: scores over time from independent reviews.
- Video and GIFs, and Latest Screenshots: new ones appear as you make them.
- Shipped: the recent changes from git, plus anything not committed yet.
- One tab for every kind of thing in the game, with search, sort and filters. Clicking anything opens a drawer with its details and a note box for that exact thing. Tell me which kinds you chose and any you left out.

Use real data and real pictures. Pull the data from the game's own tables and capture pictures from the running game. The game's own icons and portraits count. Run the game headless and muted when you capture it. Don't invent entries or draw placeholder art. If something can't be captured, or there are too many to capture, get a good set, mark the rest as not captured and tell me. Look at a sample of the pictures yourself, because automated checks miss black frames and empty shots.

Keep everything in plain JSON files you can read and write as you build. The page should refresh every few seconds without losing my clicks or what I'm typing.

From now on, this is part of how you work:

- At the start of every round, read my notes. Mark new ones as seen and put them at the top of the queue. My notes outrank your plan.
- Update your task list at every step, not at the end.
- When a note is finished, mark it done and write a short reply that shows under it.
- After each meaningful round, send 8 to 12 screenshots to a separate agent that hasn't seen your reasoning, with no hints about what changed. Get a score out of 10, a score for each area and a ranked list of defects, and add it to Ratings. Never grade your own work.
- Refresh the clips and pictures whenever the visuals change.

Before you say it's done, open the page in a real browser. Click every tab, try search, sort and filters, send a test note, confirm it reaches the notes file, then delete it. Tell me the address and anything that's missing.

Once the local page works, ask if I want it hosted so I can open it on my phone and other computers. If I do, put it on a free Vercel account behind one password, and keep a background script running that syncs your status up and my notes back. I'll handle any logins and security codes myself. If I don't want it hosted, you're done.

Paste it into Claude Code, opened in your game’s folder.

Host the workbench so I can open it anywhere

With the skill installed. The prompt above asks you this on its own.