prototype

Test a game concept's core interaction loop with a throwaway prototype.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/WindXRan/y3td --skill prototype-windxran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/prototype
Command: npx skills add https://github.com/WindXRan/y3td --skill prototype-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The prototype skill reduces the risk of building the wrong game by testing whether a core concept is fun to interact with before you invest in GDDs, architecture, or production-level work.

Core Features & Use Cases

  • Hypothesis-driven concept prototyping: Turns a vague idea into a falsifiable hypothesis with an explicit measurable signal to validate or falsify.
  • Path-based rapid validation: Routes the prototype to HTML, Engine, or Paper based on whether the hypothesis is about rules/logic or moment-to-moment feel.
  • Session checkpointing and decision verdicts: Produces a throwaway build and guides the workflow toward a PROCEED, PIVOT, or KILL recommendation, including optional spike mode for ~4-hour targeted testing.

Use Cases

  • Validate core loop fun before writing full GDD and system docs.
  • Run mid-production mechanic or technical spikes without full phase-gate overhead.
  • Quickly choose between “rules matter” (Paper/HTML) and “feel matters” (Engine).

Quick Start

Run the prototype with your concept description using the engine path: prototype "Describe the core gameplay loop and the riskiest assumption" --path engine.

Frequently Asked Questions about prototype

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate if my game prototype is fun before writing a full GDD?

You validate a game prototype by running a throwaway concept build that tests the core interaction loop, producing a PROCEED, PIVOT, or KILL decision to confirm it is fun before writing a full GDD.

What is the best way to test a game mechanic hypothesis during early development?

Testing a game mechanic hypothesis involves turning a vague idea into a falsifiable statement with a measurable signal, then validating or falsifying it through a rapid concept prototype build.

Can I run a 4-hour technical spike for a mid-production mechanic verification?

Yes, you can run a targeted technical spike for mid-production mechanic verification using spike mode, which enables approximately 4 hours of focused testing without full phase-gate overhead.

How do I choose between HTML, Engine, and Paper paths for game prototyping?

Choose between HTML, Engine, and Paper prototype paths by determining whether your hypothesis focuses on rules and logic, favoring Paper or HTML, or moment-to-moment feel, which requires the Engine path.

When should I not use a throwaway prototype for game design validation?

You should avoid throwaway prototyping for game design validation when moving past early-stage concept development, as it specifically targets pre-production hypothesis testing rather than production-level architecture.