game-dev
Build, prototype, debug, and ship game features across Unity, Unreal, Godot, and web game stacks. Use when requests involve gameplay systems, mechanics implementation, level scripting, input/camera/UI flow, save-load design, multiplayer foundations, performance profiling, content pipelines, or release-readiness planning for game projects.
Best use case
game-dev is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Build, prototype, debug, and ship game features across Unity, Unreal, Godot, and web game stacks. Use when requests involve gameplay systems, mechanics implementation, level scripting, input/camera/UI flow, save-load design, multiplayer foundations, performance profiling, content pipelines, or release-readiness planning for game projects.
Teams using game-dev should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/game-dev/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How game-dev Compares
| Feature / Agent | game-dev | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Build, prototype, debug, and ship game features across Unity, Unreal, Godot, and web game stacks. Use when requests involve gameplay systems, mechanics implementation, level scripting, input/camera/UI flow, save-load design, multiplayer foundations, performance profiling, content pipelines, or release-readiness planning for game projects.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Game Dev ## Outcome Deliver production-ready game feature slices that include implementation, validation, and clear next actions. ## Workflow 1. Clarify target player experience, platform, engine, and constraints. 2. Break work into a thin vertical slice that is testable in one session. 3. Implement deterministic core logic before visual polish. 4. Add observability early (logs, debug overlays, simple metrics). 5. Validate with explicit playtest steps and edge-case checks. 6. Report risks, tradeoffs, and follow-up tasks. ## Engine Routing - Use Unity patterns for component-driven C# gameplay and editor tooling. - Use Unreal patterns for gameplay framework classes, Blueprint/C++ boundaries, and data assets. - Use Godot patterns for scene-tree architecture, signals, and GDScript/C# node lifecycles. - Use web patterns for render loop timing, state isolation, and asset loading constraints. If the user does not specify an engine, ask once, then proceed with a pragmatic default based on existing repo signals. ## Feature Slice Standard For each requested gameplay feature: 1. Define the player-facing behavior in one paragraph. 2. Define state model and failure modes. 3. Implement core systems with minimal dependencies. 4. Integrate with input, camera, UI, and persistence as needed. 5. Add quick tuning knobs for designers (constants, data tables, scriptable configs). 6. Add smoke tests or reproducible manual verification steps. ## Debug and Performance Guardrails - Reproduce bugs with exact deterministic steps before patching. - Prefer smallest safe fix; avoid broad rewrites unless required. - Measure frame-time impact for new systems and expensive loops. - Watch allocation churn, physics/query frequency, and update loop fan-out. - Keep data flow explicit to avoid hidden coupling between gameplay systems. ## Response Contract When executing a request, return: 1. What changed and why. 2. Files/systems touched. 3. How to test quickly. 4. Remaining risks and next recommended milestone.
Related Skills
scbe-training-pair-authoring
Create prompt and response and metadata training pairs from SCBE documents, repair traces, terminal sessions, and operational workflows using the repository's canonical dataset contract and provenance rules.
scbe-spin-conversation-engine
Generate SFT training data via radial matrix conversation pivots with D&D-style combat research mode. Produces diverse, cost-effective training pairs with Sacred Tongue encoding, golden spiral problem distribution, and harmonic re-attunement.
scbe-research-training-bridge
Stage arXiv evidence and Obsidian markdown into source-grounded Hugging Face training bundles for research, review, and later SFT runs.
scbe-document-management
Consolidate overlapping docs, classify files by authority, and keep SCBE repo documents aligned with runtime truth. Use when the repo has drift between canonical docs, public docs, proposal notes, research branches, and generated evidence.
scbe-colab-bridge
Control Google Colab notebooks from Claude Code via Chrome extension. Execute cells, run terminal commands, read outputs, and manage GPU compute remotely.
scbe-claim-to-code-evidence
Map SCBE Notion technical claims, proof pages, and patent-facing architecture notes to concrete repository evidence such as code paths, tests, demos, and docs. Use when Codex needs to build a due-diligence packet, claim-to-code audit, implementation crosswalk, patent support note, or proof summary from local Notion exports and repo artifacts.
scbe-autonomous-worker-productizer
Turn SCBE automation, autonomous worker, and revenue-system notes into concrete offers, workflow packs, pilot plans, or SaaS-facing product packets. Use when Codex needs to package Notion automation pages into buyer-ready offerings, n8n/Zapier workflow designs, flock-backed worker systems, or implementation roadmaps tied to existing SCBE repo surfaces.
multi-agent-cloud-offload
Deterministically sort, bundle, verify, and offshore local files through multiple AI/model lanes while capturing training rows and method evidence. Use when Codex needs to inventory folders, batch-process files, upload them to cloud targets such as rclone-backed Google Drive, Hugging Face, or GitHub, and only delete sources after the configured number of verified targets succeed.
long-form-work-orchestrator
Run long-form engineering work in checkpointed phases with deterministic artifacts, resilience handling, and end-of-run reliability reporting.
scbe-code-scanning-ops
Operate GitHub code scanning and CodeQL remediation for SCBE repositories. Use when triaging code-scanning alerts, mapping alert classes to fix patterns, validating targeted regressions, or wiring dedicated CodeQL workflows and runbooks into the repo.
cloud-storage-local-storage-management
Audit, sort, route, and back up large Windows workspaces across local disks and cloud-sync folders without recursive mirror failures. Use when the user wants the filesystem cleaned up, cloud storage organized, backup targets chosen by free space and route quality, or hardware/storage bottlenecks identified before moving data.
video-source-verification
Use this skill for fast, traceable internet-source verification of claims from videos/articles (especially YouTube claims) before acting on them.