demo-builder

demo-builder is a skill for Claude Code from natea/fitfinder. It costs 37 tokens per session (5,535 once invoked), scanned A, original, MIT.

A game prototyping guide that turns a game concept document into a playable browser demo. It uses Three.js for the prototype and can include mechanics, a level, scoring, characters, visual assets, and music.

In plain words
What is it for?
Use it to parse a design document, build a first playable level, add basic game assets and audio, and produce an HTML, JavaScript, and CSS demo for browser playtesting.
Why use it?
It helps teams test and show a game idea before investing in full production.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: names the TodoWrite tool.

Good fit Use it to parse a design document, build a first playable level, add basic game assets and audio, and produce an HTML, JavaScript, and CSS demo for browser playtesting.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/natea/fitfinder/demo-builder
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add natea/fitfinder --skill demo-builder
Clone the repo
git clone --depth 1 https://github.com/natea/fitfinder

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for demo-builder

README.md
[![agentmods](https://agentmods.dev/badge/skills/natea/fitfinder/demo-builder/github.svg)](https://agentmods.dev/skills/natea/fitfinder/demo-builder)
Your own site
<a href="https://agentmods.dev/skills/natea/fitfinder/demo-builder"><img src="https://agentmods.dev/badge/skills/natea/fitfinder/demo-builder/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for demo-builder

Your own site · 80×15
<a href="https://agentmods.dev/skills/natea/fitfinder/demo-builder"><img src="https://agentmods.dev/badge/skills/natea/fitfinder/demo-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,535 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.05535
Opus 5 $0.00018 $0.02767
Sonnet 5 $0.00007 $0.01107
Haiku 4.5 $0.00004 $0.00553

Measured 6d ago against content hash aa63556b4ecf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

demo-builder scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/demo-builder/SKILL.md · 740 lines

How it starts

The opening of the file, as written. The whole thing — 740 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Demo Builder Skill

Purpose

This skill automatically generates playable game prototypes from game concept documents. It:

  • Parses concept documents to extract game mechanics, theme, genre
  • Generates Three.js game code using the threejs-game skill
  • Creates first playable level with scoring, objectives, characters
  • Generates assets (textures, colors, basic models)
  • Integrates music (Suno AI generation or 8-bit MIDI)
  • Produces web-ready demo that runs in browser

Output: Fully functional game demo with HTML/JS/CSS that can be played immediately.

When to Use This Skill

Use this skill when you have:

  • ✅ Game concept document (from brainstorming/design phases)
  • ✅ Need to validate gameplay quickly with playable prototype
  • ✅ Want to pitch game with interactive demo vs. static mockups
  • ✅ Require rapid prototyping for playtesting
  • ✅ Need proof-of-concept before full development investment

Prerequisites

Required Input

Game Concept Document (from brainstorming or design)

  • Location: /docs/*-game-concepts-*.md or /docs/plans/*-design.md
  • Must include: Title, description, genre, core mechanics, theme
  • Example: fps-game-concepts-market-driven-2025-10-26.md

Dependencies

  • threejs-game skill (for 3D game implementation)
  • Three.js library (loaded via CDN in generated HTML)
  • Optional: Suno API key for music generation (can use MIDI fallback)

Core Workflow

Phase 1: Concept Parsing

1. Load Game Concept

GameConcept = {
  title: string,
  description: string,
  genre: string[],  // ["FPS", "Extraction", "Co-op"]
  theme: string,    // "cyberpunk", "military", "horror", etc.
  core_mechanics: string[],
  target_persona: string,
  price_point: number | "F2P"
}

2. Extract Demo Requirements

DemoRequirements = {
  game_type: "FPS" | "third-person" | "top-down" | "side-scroller",
  camera_type: "first-person" | "third-person" | "fixed" | "isometric",
  movement_type: "WASD" | "mouse" | "touch" | "hybrid",
  primary_mechanic: "shooting" | "extraction" | "survival" | "puzzle",
  color_palette: extractColorPalette(theme),
  character_archetypes: extractCharacters(description),
  objectives: extractObjectives(description),
  music_style: extractMusicStyle(genre, theme)
}

Read the full file on GitHub · 740 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 740 lines · 37 tokens per session scan A aa63556b4ecf

Subscribe to this mod's changes

demo-builder is a skill published in the GitHub repository natea/fitfinder (4 stars, last pushed 10mo ago), licensed MIT. It adds 37 tokens to every session and 5,535 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

worker-visualizer

A real-time data/particle/simulation visualizer whose heavy compute runs in a Web Worker (off the main thread), optionally sharing memory with the UI via SharedArrayBuffer, and renders to a canvas at 60fps. Produced as a single self-contained index.html. Use when the brief asks for a "web worker", "simulation"…

nexu-io/open-design · 123 tokens

react-three-fiber

React Three Fiber 3D renderer for json-render. Use when working with @json-render/react-three-fiber, building 3D scenes from JSON specs, rendering meshes/lights/models/environments, or integrating Three.js with json-render catalogs.

vercel-labs/json-render · 54 tokens

vgpu

Build, debug, test, and optimize WebGPU projects using vgpu, its CLI, or @vgpu packages. Use for vgpu API questions, WGSL workflows, browser or Node rendering, integrations, testing, and performance work.

vercel-labs/vgpu · 51 tokens

matterjs

Use when implementing 2D physics interactions with Matter.js, including Engine/World setup, Render/Runner configuration, adding bodies and constraints, and scroll/interaction-friendly canvas scenes.

MengTo/Skills · 39 tokens

threejs-game-director

Entrypoint for building, upgrading, and finishing Three.js browser games. Routes work across the sibling threejs- skills for gameplay, graphics, UI, 3D/image/audio asset generation, debugging, and release. Use for build-a-game, upgrade, polish, premium, AAA, high-fidelity, showcase, from-scratch, endless runner…

majidmanzarpour/threejs-game-skills · 86 tokens

sceneview-web

Build 3D and WebXR (AR/VR) experiences in the browser with SceneView for Web — Filament.js (WebGL2/WASM) wrapped in a Kotlin/JS DSL and a plain-JavaScript API on window.sceneview. Use whenever the user asks for "3D in the browser", "a web model viewer", "WebXR AR/VR", or any browser 3D/AR app where the dependency is…

sceneview/sceneview · 147 tokens