Hysen LabsFABLE-SHOWCASE
an experiment in pushing the limits of one-shot prompting
One prompt, 57 demos, a week of API credits
A single prompt told Claude Fable 5 agents to burn through a week of Anthropic API credits in one day, and the result was 57 self-contained browser demos.
The experiment
This repository answers a question the author posed to a model: what happens when you prompt Fable to use up an entire week's worth of Claude usage credits at once? The README frames the whole thing as an experiment in pushing the limits of one-shot prompting. The original prompt is quoted in full, and it is informal, a challenge to spend the credits in one day and only on Fable, building as much as possible in parallel. The repo is written in HTML and carries no license in the metadata.
What the 57 files are
The output is 57 self-contained creative web demos, covering generative art, simulations, instruments, and procedural worlds. Each one is a single index.html file with zero dependencies: no build step, no CDN, no frameworks, no network requests. Open any file directly in a browser and it runs. The README says each demo was designed, built, polished, and QA-verified end to end by fleets of Claude Fable 5 agents running in parallel, in a single day.
The collections
Six collections organize the demos. Simulation and life covers boids murmuration, particle-life, slime mold, a reef, a tidepool, and an L-system garden. Generative art includes a fractal voyager, an I-Ching oracle, tarot, stained glass, and calligraphy. Physics and motion has an n-body orbital sandbox, black-hole lensing, and Chladni cymatics. Worlds and skies holds an aurora, an infinite gothic cathedral, and a cinematic ocean. Sound and music, then play and curiosities, round out the list with a light synth, pinball, and a clock zoo.
How it was built
A single prompt in Claude Code fanned out roughly 275 Fable 5 subagent runs across background multi-agent workflows. Each demo flowed through a design, build, enhance, and QA pipeline until the week's API credits ran out. Thumbnails were captured by rendering each demo in a headless browser, and the gallery embeds them as data URIs so everything stays self-contained.
What is in the repo
The structure is simple. A top-level index.html is the gallery, searchable and category-filtered, with thumbnails embedded inline. Each individual demo lives in its own index.html under the same folder, and a thumbs directory holds the captured preview images. In other words, the whole deliverable is static files you can open without a server.
Community notes