What problem does it solve?
Building action-game encounters often devolves into stacking enemy counts, producing unfair fights with offscreen damage, unreadable telegraphs, and untested difficulty spikes. This Skill provides a structured playbook for designing, tuning, and validating Three.js encounters around player decisions rather than raw actor counts.
Core Features & Use Cases
- Encounter Composition: Define objectives, arena space, enemy roles, spawn timing, hazards, player resources, exits, failure recovery, and rewards, adding one pressure source at a time.
- Fairness Guardrails: Protect readable paths, telegraphs, camera sight lines, and recovery windows while capping simultaneous committed attackers and avoiding unavoidable damage chains.
- Deterministic Validation: Create reproducible test fixtures for low-resource starts, each wave, boss phases, victory, and death/retry, tested on desktop and mobile at real camera distance.
- Use Case: A developer building a Three.js arena boss fight uses this Skill to structure three boss phases, tune spawn pacing per wave, and validate each phase with deterministic fixtures before shipping.
Quick Start
Use the design-game-encounters skill to design a three-wave arena encounter with a boss phase and deterministic test fixtures for my Three.js game.
