Sponsored by

Find leads on Reddit on auto pilot

Topic: unity

184 skills in this topic.

skill-test Validate skill files for structural compliance and behavioral correctness. Three modes: static (linter), spec (behavioral), audit (coverage report).
Donchitos/Claude-Code-Game-Studios 8,725
test-helpers 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 mock objects tailored to the project's systems. Reduces boilerplate in new test files.
Donchitos/Claude-Code-Game-Studios 8,725
design-system Guided, section-by-section GDD authoring for a single game system. Gathers context from existing docs, walks through each required section collaboratively, cross-references dependencies, and writes incrementally to file.
Donchitos/Claude-Code-Game-Studios 8,725
hotfix Emergency fix workflow that bypasses normal sprint processes with a full audit trail. Creates hotfix branch, tracks approvals, and ensures the fix is backported correctly.
Donchitos/Claude-Code-Game-Studios 8,725
qa-plan Generate a QA test plan for a sprint or feature. Reads GDDs and story files, classifies stories by test type (Logic/Integration/Visual/UI), and produces a structured test plan covering automated tests required, manual test cases, smoke test scope, and playtest sign-off requirements. Run before sprint begins or when starting a major feature.
Donchitos/Claude-Code-Game-Studios 8,725
test-setup 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. Run once during Technical Setup phase before the first sprint begins.
Donchitos/Claude-Code-Game-Studios 8,725
day-one-patch Prepare a day-one patch for a game launch. Scopes, prioritises, implements, and QA-gates a focused patch addressing known issues discovered after gold master but before or immediately after public launch. Treats the patch as a mini-sprint with its own QA gate and rollback plan.
Donchitos/Claude-Code-Game-Studios 8,725
team-audio Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.
Donchitos/Claude-Code-Game-Studios 8,725
bug-report Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context.
Donchitos/Claude-Code-Game-Studios 8,725
review-all-gdds Holistic cross-GDD consistency and game design review. Reads all system GDDs simultaneously and checks for contradictions between them, stale references, ownership conflicts, formula incompatibilities, and game design theory violations (dominant strategies, economic imbalance, cognitive overload, pillar drift). Run after all MVP GDDs are written, before architecture begins.
Donchitos/Claude-Code-Game-Studios 8,725
map-systems Decompose a game concept into individual systems, map dependencies, prioritize design order, and create the systems index.
Donchitos/Claude-Code-Game-Studios 8,725
asset-spec Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.
Donchitos/Claude-Code-Game-Studios 8,725
security-audit Audit the game for security vulnerabilities: save tampering, cheat vectors, network exploits, data exposure, and input validation gaps. Produces a prioritised security report with remediation guidance. Run before any public release or multiplayer launch.
Donchitos/Claude-Code-Game-Studios 8,725
propagate-design-change When a GDD is revised, scans all ADRs and the traceability index to identify which architectural decisions are now potentially stale. Produces a change impact report and guides the user through resolution.
Donchitos/Claude-Code-Game-Studios 8,725
bug-triage Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
Donchitos/Claude-Code-Game-Studios 8,725
team-ui Orchestrate the UI team through the full UX pipeline: from UX spec authoring through visual design, implementation, review, and polish. Integrates with /ux-design, /ux-review, and studio UX templates.
Donchitos/Claude-Code-Game-Studios 8,725
create-epics Translate approved GDDs + architecture into epics — one epic per architectural module. Defines scope, governing ADRs, engine risk, and untraced requirements. Does NOT break into stories — run /create-stories [epic-slug] after each epic is created.
Donchitos/Claude-Code-Game-Studios 8,725
reverse-document Generate design or architecture documents from existing implementation. Works backwards from code/prototypes to create missing planning docs.
Donchitos/Claude-Code-Game-Studios 8,725
prototype Rapid prototyping workflow. Skips normal standards to quickly validate a game concept or mechanic. Produces throwaway code and a structured prototype report.
Donchitos/Claude-Code-Game-Studios 8,725
content-audit Audit GDD-specified content counts against implemented content. Identifies what's planned vs built.
Donchitos/Claude-Code-Game-Studios 8,725
launch-checklist Complete launch readiness validation covering every department: code, content, store, marketing, community, infrastructure, legal, and go/no-go sign-offs.
Donchitos/Claude-Code-Game-Studios 8,725
test-flakiness 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 maintains a flaky test registry. Best run during Polish phase or after multiple CI runs.
Donchitos/Claude-Code-Game-Studios 8,725
team-polish Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.
Donchitos/Claude-Code-Game-Studios 8,725
smoke-check Run the critical path smoke test gate before QA hand-off. Executes the automated test suite, verifies core functionality, and produces a PASS/FAIL report. Run after a sprint's stories are implemented and before manual QA begins. A failed smoke check means the build is not ready for QA.
Donchitos/Claude-Code-Game-Studios 8,725