game-design-framework

Evaluate game mechanics with the 5-Component Relevance Filter and state machine documentation.

Updated May 18, 2026
One-click install
npx skills add https://github.com/afovea/game-dev-skills --skill game-design-framework-afovea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: game-design-framework
Source: https://github.com/afovea/game-dev-skills/tree/main/plugins/game-team/skills/game-design-framework
Command: npx skills add https://github.com/afovea/game-dev-skills --skill game-design-framework-afovea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the lack of structured decision-making in game design by replacing intuition-based balancing with a rigorous, evidence-based framework for mechanics and systems.

Core Features & Use Cases

  • 5-Component Relevance Filter: Evaluate whether a mechanic truly belongs in your game based on clarity, motivation, response, satisfaction, and fit.
  • Numbers Policy: Establish a standardized, tiered approach to balance, ensuring every tuning value has a source, a target, and a defined confidence level.
  • State Machine Checklist: Ensure player actions are fully specified by documenting every state from startup to recovery, preventing "floaty" or "unresponsive" feel.
  • Use Case: Use this when you need to justify a balance change to a lead designer or when you are stuck on why a specific combat mechanic feels "off" to players.

Quick Start

Invoke the game-design-framework skill to evaluate the current dash mechanic against the 5-Component Relevance Filter.

Frequently Asked Questions about game-design-framework

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

FAQPage Schema
How do I evaluate if a game mechanic truly belongs in my design?

Evaluate game mechanics using a 5-Component Relevance Filter that checks clarity, motivation, response, satisfaction, and fit. This structured methodology replaces intuition-based design decisions with evidence-based analysis to determine mechanic coherence.

What's the best way to balance game mechanics and numerical tuning values?

Balance game mechanics using a standardized Numbers Policy that ensures every tuning value has a defined source, target, and confidence level. This tiered approach establishes rigorous numerical balance across combat systems and player interactions.

How do I document player state machines to fix unresponsive combat feel?

Document player state machines using a standardized checklist that specifies every state from startup to recovery. This ensures all player actions are fully defined, preventing floaty or unresponsive combat feel during playtesting.

Why does my combat mechanic feel off to players during playtesting?

Combat mechanics feel off when state machine documentation is incomplete, missing transitions from startup to recovery. Analyze playtest feedback against the 5-Component Relevance Filter to identify gaps in clarity, response, or satisfaction.

How do I justify a balance change to a lead designer?

Justify balance changes by applying the Numbers Policy framework, which assigns a source, target, and confidence level to every tuning value. This evidence-based approach replaces intuition with structured methodology for design documentation.

When do I need a structured game design framework for mechanics?

You need a structured game design framework when replacing intuition-based balancing with rigorous methodology for mechanics and systems. Apply it during combat tuning, playtest analysis, and game design documentation to ensure balance and coherence.