prototype

Rapid game concept validation uses disposable prototypes to test mechanics before full development. It creates a lightweight implementation in an isolated prototypes/[concept-name]/ directory to evaluate feasibility and generate a structured report within a 1-3 day scope.

To create a minimal viable prototype, provide a concept description to generate disposable files under a dedicated prototypes/[concept-name]/ directory. All files use PROTOTYPE headers, and the workflow concludes by exporting a structured REPORT.md documenting assumptions, methods, and improvement paths.

Yes, this rapid validation workflow applies to early-stage concept testing across any game idea, engine, or tech stack. It requires no specific dependencies, focusing purely on generating lightweight, disposable implementations to validate core mechanics regardless of the underlying technology.

The best way to document game prototype results is generating a structured REPORT.md file. This report captures assumptions, testing methods, results, and improvement paths, providing clear communication artifacts for evaluating whether a concept should advance to production.

Prototype code should not be imported into production because it is explicitly designed to be disposable. This constraint ensures quick learning cycles and prevents unvalidated, low-quality mechanics from contaminating the main codebase, keeping production development clean and stable.

You should limit game prototype scope to 1-3 days of effort to ensure rapid learning cycles. This time constraint forces focus on validating core assumptions quickly, preventing prototype projects from turning into prolonged development efforts that delay decision-making.