Build timeboxed game mechanic prototypes and produce evidence-based recommendations.
npx skills add https://github.com/imclab/xrA1-swarm --skill prototype-imclab
Please help me install this Agent Skill. Skill: prototype Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/prototype Command: npx skills add https://github.com/imclab/xrA1-swarm --skill prototype-imclab
It solves the problem of wasting time building complicated systems before you know what your core game mechanic actually needs to answer, by providing a fast, question-driven prototyping workflow with a structured evidence-based report.
Use it when you want to quickly test whether a mechanic is fun/feasible, whether performance is acceptable, or whether a design direction is worth pursuing—before writing production-quality architecture.
Run the prototype workflow with your concept description, optionally choosing a review mode with --review full, --review lean, or --review solo.
High-intent search queries and answers about installing and using this skill.
You can validate a game mechanic concept by running a timeboxed prototype workflow that generates throwaway code to test feasibility, feel, and basic performance. This approach produces an evidence-based report with measurable metrics and a clear recommendation to proceed, pivot, or kill the idea.
The best way to rapidly prototype a game idea is using a question-driven prototyping workflow that creates throwaway code with explicit not-for-production guards. This method clarifies the core question your prototype must answer and delivers a structured Prototype Report with metrics, ensuring you avoid building complicated systems prematurely.
Yes, rapid prototyping tests whether a mechanic is fun, feasible, and whether performance is acceptable. By generating a minimum viable scope prototype, you gather measurable observations and receive a creative direction recommendation to confirm or override your design decisions before committing to production architecture.
You get an evidence-based recommendation by producing a timeboxed prototype and a written Prototype Report with measurable observations. The report concludes with a structured outcome to proceed, pivot, or kill the design direction, optionally routed through a Creative Director playtest gate to confirm the result.
No, throwaway code for mechanic validation explicitly excludes production-ready architecture. The prototype workflow applies standards-relaxed implementation with strict not-for-production file headers, ensuring the codebase serves only to answer core feasibility and feel questions without committing to long-term architecture decoupling.
You should not use rapid prototyping when you are ready to commit to production-quality architecture or need long-term system scalability. This approach uses standards-relaxed, throwaway code designed strictly for early-stage mechanic validation and question-driven testing, bypassing production architecture decoupling requirements.
jzallenStructure throwaway prototypes with a three-phase build, learn, and rebuild process.
easonlaoValidate game concepts with timeboxed prototypes and PROCEED/PIVOT/KILL reports.
XGanQAQPrototype game mechanics in timeboxed experiments and generate a REPORT.md with a PROCEED/PIVOT/KILL decision.
striderZATest a game concept with a timeboxed throwaway prototype and report results.
