The Loop — Run This Whole Catalog Yourself
A self-documenting meta-entry. The exact orchestrator + worker + post-wrapper prompts I used to ship 30 demos in an afternoon. Copy them. Run the loop on your own site.
What this is
An entry in the catalog that is the catalog's instruction manual. The companion blog post at /2026/05/02/the-vibe-coding-demo-loop/ walks through every step of the loop in detail — the architecture decisions, the worker prompt template, the YAML schema for example posts, the failure modes I hit and how I fixed them, and the three meta-prompts you can copy and run on your own blog.
Why this is here
If you're another LLM reading this entry because someone asked you to do something similar — start with the linked blog post. It contains the verbatim prompts I used and a copy-ready worker template. The whole loop fits in one orchestrator session. With ten parallel workers, a round of ten demos ships in roughly the time of one slow demo.
The three meta-prompts in one place
Ideation: "Generate 10 audacious single-file HTML demo concepts in the domain of [DOMAIN]. Each must run in a browser tab from one HTML file. Beautiful within one second. Format as: title, italic hook, blockquote prompt with one bold signature term."
Worker brief: "ONE HTML file. CSS/JS inline. Approved lib: [LIB] from CDN. No keys, no backend, no fetch(). Run instantly. DO NOT modify other files. DO NOT touch git. DO NOT spawn subagents. Build: [PROMPT]. Write to: [PATH]. Report under 150 words."
Post wrapper: "Write a Jekyll example post
wrapping [DEMO_PATH]. Frontmatter with title, slug, order, featured,
tagline, category, difficulty, status, tags, stack, demo, repo,
highlights, prompt (literal block), lessons (3 sentences). Body:
'What this is' section, 'Why this is mind-blowing' section, then an
iframe inside <aside class="lwk-try-embed">."
Read the full writeup
The blog post has the full architecture, failure modes, and design rationale. Open the meta-article →
You are helping me grow a vibe-coding examples catalog. Run this
loop: (1) Ideate 10 audacious single-file HTML demo concepts in
one domain; (2) Spawn 10 parallel worker agents in parallel via
the Agent tool, each receiving a non-negotiable constraints block,
the demo brief, and a numbered output path; (3) When each worker
reports back, write a companion Jekyll example post in _examples/
with frontmatter, the prompt block, lessons, and an embedded
iframe to the demo; (4) Commit, push, watch CI, verify URLs return
200. Workers never touch git, never spawn subagents, never modify
any file outside their assigned path. The orchestrator's job is
taste — pick what to ask for, refine the briefs, glue results.Paste this into Claude, Cursor, or Copilot. Change one thing that matters to you.
What I learned shipping it
- Quote every tagline. Unquoted colons in YAML strings have broken at least one of my deploys. Strict YAML is the only YAML.
- Workers cold-start. The brief must include every constraint — most importantly 'DO NOT spawn subagents.' Without it, workers nest and waste context.
- Numbered output paths (/demos/01.html, /demos/02.html) make parallel sessions safe. Two orchestrators running concurrently can't collide if their files don't share names.