claude▌

### Ux Design - description: "Guided, section-by-section UX spec authoring for a screen, flow, or HUD. Reads game concept, player journey, and relevant GDDs to provide context-aware design guidance. Produces ux-spec. - argument-hint: "[screen/flow name] or 'hud' or 'patterns'" - allowed-tools: Read, Glob, Grep, Write, Edit, AskUserQuestion, Task

### Team Narrative - description: "Orchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design. - argument-hint: "[narrative content description]" - allowed-tools: Read, Glob, Grep, Write, Edit, Task, AskUserQuestion, TodoWrite

### Test Flakiness - description: "Detect non-deterministic (flaky) tests by reading CI run logs or test result history. Aggregates pass rates per test, identifies intermittent failures, recommends quarantine or fix, and - argument-hint: "[ci-log-path | scan | registry]" - allowed-tools: Read, Glob, Grep, Write, Edit, Bash

### Ux Review - description: "Validates a UX spec, HUD design, or interaction pattern library for completeness, accessibility compliance, GDD alignment, and implementation readiness. Produces APPROVED / NEEDS REVISIO - argument-hint: "[file-path or 'all' or 'hud' or 'patterns']" - allowed-tools: Read, Glob, Grep

### Team Release - description: "Orchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment." - argument-hint: "[version number or 'next']" - allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion, TodoWrite

### Test Helpers - description: "Generate engine-specific test helper libraries for the project's test suite. Reads existing test patterns and produces tests/helpers/ with assertion utilities, factory functions, and moc - argument-hint: "[system-name | all | scaffold]" - allowed-tools: Read, Glob, Grep, Write

### Team Qa - description: "Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a - argument-hint: "[sprint | feature: system-name]" - allowed-tools: Read, Glob, Grep, Write, Task, AskUserQuestion

### Test Setup - description: "Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. R - argument-hint: "[force]" - allowed-tools: Read, Glob, Grep, Bash, Write

### Team Level - description: "Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation." - argument-hint: "[level name or area to design]" - allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion, TodoWrite

### Regression Suite - name: regression-suite - description: "Map test coverage to GDD critical paths, identify fixed bugs without regression tests, flag coverage drift from new features, and maintain tests/regression-suite.md. Run after implementi - argument-hint: "[update | audit | report]"