prototype

A game prototype uses throwaway code to validate a mechanic in a timeboxed experiment. It isolates the core mechanic from production architecture to test whether the concept is worth pursuing, ending with a structured report and a go/no-go decision.

A prototype report captures the hypothesis, approach, observed results, and measurable metrics gathered during testing. This documentation provides concrete evidence for a final PROCEED, PIVOT, or KILL verdict during the creative review process.

Claude Code can run a rapid prototyping workflow that converts a vague idea into a focused question and throwaway implementation. It generates a prototype directory and enforces timeboxed experiments to validate mechanics without production-quality engineering.

You run a creative review gate by triggering a full mode playtest evaluation. This creative-director gate reviews the prototype report and measured metrics to confirm, modify, or override the prototyper’s recommendation with a final decision.

You should avoid throwaway code when moving beyond mechanic validation into production-quality engineering. Throwaway code is strictly for short timeboxed experiments and single-mechanic alignment checks, not for building scalable architecture or final game systems.