Kaynexis-Agentic-Game-Studio

Design or tune a combat loop including enemy roles, feedback, pacing, damage model, and skill expression. Use for combat-heavy slices and balance passes.

Audit or frame engine-specific project setup, folder conventions, packages/plugins, and build assumptions. Use for Godot, Unity, or Unreal setup and repo structure decisions.

Specify a single player mechanic with verbs, inputs, feedback, tuning surfaces, edge cases, and testability. Use for movement, abilities, interactions, or systemic verbs.

Design or implement one UI flow with screen states, transitions, copy needs, and validation. Use for menus, HUD flows, settings, or onboarding screens.

Audit a feature or build for control, readability, timing, color, subtitle, and assist-option risks. Use during feature review or release prep.

Write or revise an ADR for technical decisions with significant maintenance, performance, or pipeline impact. Do not use for tiny local refactors.

Create a lightweight art direction pack with pillars, references, asset priorities, readability, and pipeline constraints. Use early in visual development or when coherence drifts.

Create an audio direction pack covering pillars, mix hierarchy, sonic language, and implementation priorities. Use early or when the game lacks coherent sound direction.

Frame service contracts, auth assumptions, matchmaking/persistence scope, and operational boundaries. Use before serious backend implementation or live features.

Convert a vague bug into reproducible steps, hypotheses, severity, owner, and next action. Use for crash, regression, UI, gameplay, or content bugs.

Design or harden CI/build/package flows, environment assumptions, versioning, and artifacts. Use for reproducible builds and release engineering.

Plan playtests, betas, patch-note communication, feedback intake, and community moderation loops. Use around demos, betas, and release updates.

Review content and product structure for age-rating, disclosure, privacy, and player-safety implications. Use when shipping publicly across stores or regions.

Audit a build and process for certification-style requirements, submission evidence, and likely blockers. Use for console or tightly regulated platform releases.

Shape how assets, scripts, dialogue, or level content move from authoring into the game safely and repeatably. Use when content throughput or consistency is weak.

Define event schemas, funnels, metrics, and privacy-safe instrumentation. Use when a feature needs measurement, balancing data, or live observation.

Design or rebalance currencies, sinks, progression prices, drop rates, and anti-exploit safeguards. Use for shops, crafting, meta loops, or F2P economies.

Turn a feature idea into a buildable contract with player outcome, acceptance criteria, risks, and validation. Use before implementing anything non-trivial.

Implement one validated gameplay slice with acceptance criteria, touched files, and explicit validation. Use for scoped mechanics, interactions, or player-facing feature work.

Triage an incoming request and recommend the best next skill, agents, docs, and validation plan. Use first when the task is ambiguous, broad, or cross-functional. Do not use for already well-scoped single-step edits.

Frame a level blockout with routing, pacing, encounter slots, visibility, gating, and teaching beats. Use before detailed art or scripting.

Plan a lightweight live-ops cadence with beats, offers/events, rewards, and operational risks. Use for service-like updates without overengineering.

Prepare text, UI, formatting, glossary, and extraction workflow for localization. Use before shipping in multiple languages or when text structure changes heavily.

Create a concise beat plan for announce/demo/update moments, with core message, assets, proof points, and community follow-up. Use for festivals, demos, betas, or patch launches.

Shape between-run or long-term progression with unlocks, retention beats, reset value, and pacing. Use for roguelites, service games, or multi-session arcs.

Adapt a feature or build for mobile performance, controls, memory, battery, and session design. Use for iOS/Android releases or mobile-focused slices.

Review monetization design for fairness, player trust, platform constraints, and ethical guardrails. Use for F2P offers, bundles, ads, battle passes, or economy pressure.

Design or implement one multiplayer feature slice with authority model, sync expectations, latency assumptions, and desync validation. Use for online or co-op work.

Organize story beats, dialogue production, branching constraints, and implementation-ready narrative docs. Use for narrative-heavy features or content pipelines.

Frame and execute a minimal-risk hotfix with rollback posture, targeted validation, and communication notes. Use for urgent crashes, blockers, or severe regressions.

Frame a performance investigation or optimization pass with budgets, measurements, bottlenecks, and smallest high-impact fixes. Use for FPS, load times, memory, thermal, or battery issues.

Map a PC/console/mobile/web port into concrete deltas for input, performance, compliance, assets, and release sequencing. Use before or during porting work.

Capture what happened, what worked, what failed, and what should change after a sprint, milestone, incident, or release. Use after meaningful outcomes.

Scan the repository for the highest-impact gaps across code, docs, tests, build pipeline, and release risk. Use when you need a fast health check before starting work.

Design puzzle logic, affordances, hinting, failure recovery, and readability. Use for spatial, systemic, or sequence puzzles.

Create a lean but meaningful test matrix from a feature or milestone. Use before calling a feature done or preparing a playtest/release.

Shape mission/quest structure with objectives, branching, dependencies, fail states, and recovery logic. Use for narrative or systemic missions.

Run a ship/no-ship review that aggregates quality, cert, performance, and communication readiness into a clear recommendation. Use before demo, beta, or launch.

Design or implement save/load behavior, checkpoints, migrations, and corruption recovery. Use whenever state persistence changes.

Reduce an overgrown milestone into a realistic vertical slice with explicit cuts, preserves, and risks. Use when the plan is too broad, behind schedule, or internally inconsistent.