game__directing

Generate a Design Brief and validation plan before writing code.

1|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/erikhazzard/vasir --skill game-directing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: game__directing
Source: https://github.com/erikhazzard/vasir/tree/main/.agents/skills/game__directing
Command: npx skills add https://github.com/erikhazzard/vasir --skill game-directing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Directs game design by producing a compact, enforceable Design Brief and validation plan before any code is written, preventing incoherent games that feel random and ensuring alignment with the intended vision for iOS touch-first experiences.

Core Features & Use Cases

  • Produces a Design Brief that defines the emotional target, core mechanics, and validation criteria before any implementation.
  • Enforces a three-system constraint and coherence lenses to keep scope tight and focused.
  • Validates that generated code and assets align with the defined brief, reducing rework and drift.
  • Use Case: kick off a new game concept and lock the design before prototyping.

Quick Start

Provide a Design Brief outlining vision, constraints, and three systems before any implementation begins.

Frequently Asked Questions about game__directing

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

FAQPage Schema
How do I create a game design brief before writing any code?

To create a game design brief, define your emotional target, core mechanics, and validation criteria. This approach enforces a three-system constraint and design-before-code workflow to lock the creative vision before any implementation begins.

What is the best way to validate that my game prototypes align with the original design?

The best way to validate game prototype alignment is to use a pre-defined validation plan and coherence lenses. This ensures generated code and assets match your design brief, reducing rework and preventing scope drift.

How do I keep my iOS game scope tight and focused during early concept development?

To keep your iOS game scope tight, enforce a three-system constraint and apply coherence guidelines during concept development. This prevents incoherent games that feel random and ensures strict alignment with your intended vision.

Does this game design approach work for touch-first iOS experiences?

Yes, this game design approach is specifically tailored for iOS touch-first experiences. It directs game design by producing a compact, enforceable design brief to ensure your mechanics fit the platform's constraints.

Why does my game feel random and lack coherence during development?

Your game feels random and lacks coherence because development began without a strict design brief. Establishing an explicit validation plan and coherence guidelines before writing code prevents this drift and maintains your intended vision.

What are the limitations of a three-system constraint in game design?

The limitation of a three-system constraint is that it strictly restricts your game's scope to exactly three systems. While this keeps the design focused and tight, it may limit complex mechanics that exceed the defined system boundaries.