skills.rest
MARUCIE
MARUCIECOMMUNITY
Explore all skills by this author →
GitHub

prototype

Builds timeboxed throwaway prototypes and generates structured validation reports for game concepts.

1|Updated Mar 18, 2026
Search Tags:#game development#prototyping#concept validation#timeboxing#throwaway code#mechanic testing#decision report
One-click install
npx skills add https://github.com/MARUCIE/openclaw-foundry --skill prototype-marucie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/MARUCIE/openclaw-foundry/tree/main/web/public/packs/product-manager/skills/prototype
Command: npx skills add https://github.com/MARUCIE/openclaw-foundry --skill prototype-marucie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It answers whether a new game concept or mechanic is worth building by producing a minimal, disposable prototype and an evidence-based decision report, instead of committing to full production development upfront. ## Core Features & Use Cases - Question-First Framing: Forces the prototype to answer one explicit core question rather than a feature checklist. - Isolated Throwaway Code: Builds the prototype in a dedicated prototypes/[concept-name]/ directory with relaxed standards, hardcoded values, and placeholder assets, strictly separated from production code. - Structured Decision Report: Generates a REPORT.md with hypothesis, approach, results, metrics, and a PROCEED / PIVOT / KILL recommendation. - Use Case: Before greenlighting a new combat mechanic, run a one-day prototype to test whether the timing window feels responsive, then archive the report in the decision log. ## Quick Start Ask the agent to prototype the concept "dash mechanic with 200ms input buffer" and produce a validation report with a proceed or kill recommendation.

Frequently Asked Questions about prototype

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

FAQPage Schema
How do I validate a game mechanic before building it?▼

Define one core question the mechanic must answer, then build a minimal timeboxed prototype in an isolated directory with relaxed standards. After testing, generate a structured report with results and a PROCEED, PIVOT, or KILL recommendation.

What should a prototype validation report include?▼

A prototype report should include the hypothesis, approach taken, observed results, measurable metrics like frame time or iteration count, and a clear recommendation. It should also outline production requirements if proceeding or lessons learned if killing the concept.

Can prototype code be reused in production?▼

No, prototype code must never be imported into production and production code must never import from prototype directories. If the recommendation is PROCEED, the production implementation is written from scratch.

How long should a game prototype take to build?▼

Prototype effort should be timeboxed to roughly one to three days of work. If the scope starts growing beyond that, stop and reassess whether the core question can be simplified.

When should I kill a prototype instead of proceeding?▼

Kill the concept when test results show the core hypothesis does not hold, such as unresponsive feel or failed metrics. Archive the structured report in the decision log so the reasoning is preserved for future reference.

Related Skills

Explore More Product & Management Skills→
pckienuitpckienuit

game-design

Structure game design ideas into core loops, mechanics, balancing, and progression guidance.

Community
Intermediate
alirezarezvanialirezarezvani
110

roadmap-generator

Convert architecture designs into phased roadmaps with Epics, Stories, and Tasks.

Community
Advanced
aiguy611aiguy611

playtesting

Coordinate structured playtesting workflows to surface bugs, usability issues, and balance problems.

Community
Intermediate
FrancisVargaFrancisVarga

prototype

Build minimal game prototypes to test falsifiable hypotheses and output a PIVOT, KILL, or PROCEED verdict.

Community
Advanced