igorkramar/ludoscope

Specify NPC and game-agent goals, observations, actions and state transitions with bounded behavioral tests.

Compare formal game balance variants using explicit metrics, bounded seeded simulations and transparent assumptions.

Develop distinct game concepts, audience assumptions, experience goals and design pillars before choosing mechanics.

Adversarially test explicit game rules for bypasses, dominant strategies, softlocks and unintended resource loops.

Audit sources, sinks, production, exchange and bounded resource cycles with explicit economic rules.

Investigate conditional cross-system chains, feedback and reproducible emergent scenarios with player relevance.

Map intended player experience to actions, rules, feedback, learning and a testable player journey.

Audit available game artifacts, design consistency, evidence gaps and prioritized risks without claiming exhaustive code understanding.

Review control response and audiovisual feedback using actual timing, input and motion artifacts where available.

Route game-design work through experience-first workflows, evidence-aware project context, formal checks and explicit experiments.

Design a mechanic as player actions, explicit rules, state transitions, feedback, dependencies and testable experience hypotheses.

Check authored canon, branching prerequisites and systemic narrative consequences without overwriting established story decisions.

Design testable playtest experiments and interpret real CSV or JSON observations with sample and evidence limits.

Specify procedural generator validity, coverage, repeatability and distribution tests without executing untrusted generators.

Design knowledge and capability progression, prerequisites and mastery tests without assuming RPG leveling.

Analyze explicit interactions, dependency graphs, feedback loops and change impact across game systems.

Review supplied UI artifacts for state visibility, feedback, learning, error recovery and accessibility hypotheses.