About this skill

Problem

Game design work often splits across worldview, systems, economy, monetization, and technical assessment. Early concepts can lack an executable boundary, reviews may rely on experience, and teams can struggle to tell whether a mechanic is a reskin or a rule-level innovation. This skill targets indie teams and commercial projects by turning design discussion into reviewable documents and config-ready tables.

How It Works

It organizes output around full design document generation, covering worldview, system, numerical, level, UI/UX, story, and operations modules. It can produce project-level document structure, config table templates, requirement notes, and Mermaid flow diagrams.
In review mode, it checks completeness, consistency, and technical, cost, or schedule risk, then proposes experience, balance, and monetization improvements. It can also structure worldview frameworks, historical timelines, faction relations, and cultural geography; produce attribute systems, growth curves, balance analysis, and economic circulation models; and output monetization models, activity cycles, pricing strategy, and data benchmarks.
For concept generation, it follows a pipeline of breakpoint decomposition, concept matrix generation, candidate concepts, novelty filtering, quality checks, scoring, and MVP planning. It screens out low-scoring options against thresholds such as Originality, Gameplay Impact, and Indie Feasibility.

Boundaries

It is best suited to early design, document review, concept validation, and Unity-friendly indie prototype discussion. It does not replace engine implementation, art production, or market validation. Numeric, pricing, and competitor claims still need calibration with project data, especially for compliance, security, or live-ops decisions.

Screenshots

Use Cases

Indie developers validating a Unity prototype by generating core gameplay, MVP scope, and cuttable feature lists.
Design teams reviewing system documents to check numerical, combat, and economic consistency and list risks.
Live-ops planners preparing seasonal events with config tables, pricing tiers, and ARPU/LTV benchmark notes.
Small teams structuring worldview settings, faction relations, timelines, and implementable story-level documents.

Best For

Solo or 1-5 person indie developers who want to validate a rule-innovative mechanic in Unity quickly.
System or numerical designers who need to turn combat, progression, and economy systems into reviewable documents.
Game producers who need to assess engine choice, server architecture, and team sizing risks before kickoff.
Live-ops planners who need seasonal events, pricing strategy, and monetization data benchmarks.