Tag
9 pages tagged “Claude Code”.
9 pagesClear filters
How to split game work between separate AI agents (planner, builders, playtester, reviewer), connect them with task cards, hand-off notes and screenshot evidence, stop them undoing each other, and keep token costs in check.
jay88 had Claude Opus 5.5 build a Three.js pumpkin you carve with four tools and then light, in one Claude Code session. The prompt was two lines; the real work is the carve-map technique the model chose.
Stefan Vaskevich opens the local workspace he makes games in: chats beside project pages, saved skills, MCPs for the engines, and a 36-hour Unity run documented card by card.
Meng To used the open-source Anatomy skill to turn one prompt into an animated SVG explainer of Seedream's image layers. The prompt, the one follow-up, and how the skill works.
Meng To is building an icon-and-illustration-to-3D tool with Opus 5.5: presets, materials, bases and animated backdrops. How it is structured, and where an SVG-to-3D pipeline breaks.
In a 45-minute tutorial Meng To shows how he builds web apps with Claude Code and Codex: meeting notes to baseline, one thread per feature, then an AI API and Stripe. The method and the three prompts.
A free browser tool rebuilds any real city block from OpenStreetMap and elevation data, then draws it as manga line art, screentone and solid black. Here's the three-buffer line trick, and how to rebuild a small version with an AI coding model.
In Anthropic's walkthrough, a coordinator splits one speed goal into 8 threads, each on its own branch with its own PR. Here's how to apply it to a web game, plus the quota and access limits.
nicekate made a 41-second explainer with the open-source Anatomy skill: a boxes-and-arrows diagram that says nothing, then the same idea built as a moving pin-tumbler lock. Here's its structure and how to use it for your own tech explainers.
