prototype

Validate unproven game concepts through throwaway prototypes and structured PROCEED/PIVOT/KILL verdicts.

Updated Jul 22, 2025
One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill prototype-michaelsolati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/prototype
Command: npx skills add https://github.com/MichaelSolati/mkai --skill prototype-michaelsolati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Game development teams often waste weeks or months writing full game design documents and building production-ready code for unproven core concepts, leading to massive sunk cost if the core idea isn't fun or viable. This Skill eliminates that risk by letting you test the core fun of your game idea in 1-3 days with a throwaway prototype before investing in full design and production.

Core Features & Use Cases

  • Multi-path prototyping: Supports HTML browser prototypes for puzzle/logic games, native engine builds for action/feel-focused games, and paper-based playtests for strategy/rules-heavy games, automatically recommending the best path for your genre.
  • Structured verdict system: Produces a clear PROCEED, PIVOT, or KILL recommendation backed by playtest observations, with built-in guardrails like a 3-PIVOT kill rule to avoid sunk cost traps.
  • Mid-production spikes: Supports lightweight ~4-hour spikes to test specific mechanics, technical approaches, or performance questions mid-production without full phase gate overhead.
  • Use case: A solo indie dev with a new 2D platformer idea can run an engine prototype to test if their grapple hook mechanic feels good before writing 50+ pages of game design documentation.

Quick Start

Use the prototype skill to validate your new 2D platformer grapple hook concept before writing any game design documents.

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 concept before writing full game design documentation?

To validate a game concept, build a fast throwaway prototype to test core mechanics and fun before investing in full game design documentation. This approach tests viability in 1-3 days, preventing wasted production effort on unproven ideas.

What is the best way to test game mechanics for an indie game prototype?

The best way to test game mechanics is using throwaway prototypes tailored to your genre: HTML browser prototypes for puzzle games, native engine builds for action games, and paper-based playtests for strategy games to evaluate core feel and rules.

When should I kill or pivot a game prototype during development?

You should kill or pivot a game prototype based on documented playtest observations using a structured PROCEED, PIVOT, or KILL verdict system. It includes a 3-PIVOT kill rule to avoid sunk cost traps and inform downstream design decisions.

Can I run a short mechanic testing spike during mid-production?

Yes, you can run lightweight mid-production spikes for mechanic testing or technical performance questions. These targeted throwaway prototypes are capped at a 4-hour effort to test specific design questions without full phase gate overhead.

Does paper-based playtesting work for validating strategy game rules?

Yes, paper-based playtesting works for validating strategy and rules-heavy game concepts. It serves as an effective throwaway prototyping path to test rule systems and core viability before committing to native engine builds or full production.