MCPInstall

game-tools-workflows

Game development tools, asset pipelines, version control, build systems, and team development workflows for efficient production.

Installs
105
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/pluginagentmarketplace/custom-plugin-game-developer --skill game-tools-workflows
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads game-tools-workflows automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Game Development Tools & Workflows

Development Tool Stack

┌─────────────────────────────────────────────────────────────┐
│                    GAME DEV TOOL STACK                       │
├─────────────────────────────────────────────────────────────┤
│  ENGINE: Unity / Unreal / Godot                             │
│                                                              │
│  IDE: Visual Studio / Rider / VS Code                       │
│                                                              │
│  VERSION CONTROL:                                            │
│  Git + LFS (indie) / Perforce (large teams)                │
│                                                              │
│  ART TOOLS:                                                  │
│  Blender / Maya / Substance Painter / Photoshop            │
│                                                              │
│  AUDIO:                                                      │
│  Wwise / FMOD / Reaper / Audacity                          │
│                                                              │
│  PROJECT MANAGEMENT:                                         │
│  Jira / Notion / Trello / Linear                            │
│                                                              │
│  COMMUNICATION:                                              │
│  Slack / Discord / Teams                                    │
└─────────────────────────────────────────────────────────────┘

Git Workflow for Games

GIT BRANCHING STRATEGY:
┌─────────────────────────────────────────────────────────────┐
│                                                              │
│  main ─────●─────────●─────────●─────────● (releases)      │
│             ↑         ↑         ↑         ↑                 │
│  develop ──●──●──●───●──●──●───●──●──●───● (integration)   │
│             ↑  ↑      ↑  ↑                                  │
│  feature/X─●──●      ●──●                                   │
│                                                              │
│  BRANCH TYPES:                                               │
│  main:       Production releases only                       │
│  develop:    Integration branch, daily builds               │
│  feature/*:  New features, short-lived                      │
│  fix/*:      Bug fixes                                      │
│  release/*:  Release preparation                            │
└─────────────────────────────────────────────────────────────┘

GIT LFS CONFIGURATION:
┌─────────────────────────────────────────────────────────────┐
│  .gitattributes:                                             │
│  *.psd filter=lfs diff=lfs merge=lfs -text                 │
│  *.fbx filter=lfs diff=lfs merge=lfs -text                 │
│  *.wav filter=lfs diff=lfs merge=lfs -text                 │
│  *.mp3 filter=lfs diff=lfs merge=lfs -text                 │
│  *.png filter=lfs diff=lfs merge=lfs -text                 │
│  *.tga filter=lfs diff=lfs merge=lfs -text                 │
│  *.zip filter=lfs diff=lfs merge=lfs -text                 │
└─────────────────────────────────────────────────────────────┘

Commit Convention

COMMIT MESSAGE FORMAT:
┌─────────────────────────────────────────────────────────────┐
│  PREFIX: Description (max 50 chars)                         │
│                                                              │
│  PREFIXES:                                                   │
│  feat:     New feature                                      │
│  fix:      Bug fix                                          │
│  art:      Art/visual changes                               │
│  audio:    Sound/music changes                              │
│  level:    Level design changes                             │
│  refactor: Code restructuring                               │
│  perf:     Performance improvements                         │
│  test:     Test additions/changes                           │
│  ci:       CI/CD changes                                    │
│  docs:     Documentation                                    │
│                                                              │
│  EXAMPLES:                                                   │
│  feat: Add double jump ability                              │
│  fix: Resolve player falling through floor                  │
│  art: Update hero character textures                        │
│  perf: Optimize enemy spawning system                       │
└─────────────────────────────────────────────────────────────┘

Build Automation

# ✅ Production-Ready: Build Script
import subprocess
import os
from datetime import datetime

class GameBuilder:
    def __init__(self, project_path: str, unity_path: str):
        self.project_path = project_path
        self.unity_path = unity_path
        self.build_number = self._get_build_number()

    def build(self, platform: str, config: str = "Release"):
        build_path = f"Builds/{platform}/{self.build_number}"

        args = [
            self.unity_path,
            "-quit",
            "-batchmode",
            "-projectPath", self.project_path,
            "-executeMethod", "BuildScript.Build",
            f"-buildTarget", platform,
            f"-buildPath", build_path,
            f"-buildConfig", config,
            "-logFile", f"Logs/build_{platform}.log"
        ]

        result = subprocess.run(args, capture_output=True)

        if result.returncode != 0:
            raise Exception(f"Build failed: {result.stderr}")

        return build_path

    def _get_build_number(self) -> str:
        return datetime.now().strftime("%Y%m%d.%H%M")

Team Workflow

AGILE SPRINT WORKFLOW:
┌─────────────────────────────────────────────────────────────┐
│  DAY 1: Sprint Planning                                      │
│  • Review backlog                                           │
│  • Commit to sprint goals                                   │
│  • Break into tasks                                         │
├─────────────────────────────────────────────────────────────┤
│  DAILY: Standup (15 min)                                    │
│  • What did you do?                                         │
│  • What will you do?                                        │
│  • Any blockers?                                            │
├─────────────────────────────────────────────────────────────┤
│  CONTINUOUS: Development                                    │
│  • Work on tasks                                            │
│  • Daily builds/tests                                       │
│  • Code reviews                                             │
├─────────────────────────────────────────────────────────────┤
│  PLAYTEST: Mid-sprint                                       │
│  • Team plays current build                                 │
│  • Gather feedback                                          │
│  • Adjust priorities                                        │
├─────────────────────────────────────────────────────────────┤
│  END: Sprint Review + Retro                                 │
│  • Demo completed work                                      │
│  • What went well/poorly?                                   │
│  • Improvements for next sprint                             │
└─────────────────────────────────────────────────────────────┘

🔧 Troubleshooting

┌─────────────────────────────────────────────────────────────┐
│ PROBLEM: Merge conflicts in scene files                     │
├─────────────────────────────────────────────────────────────┤
│ SOLUTIONS:                                                   │
│ → Use prefabs instead of scene objects                      │
│ → Smart merge tools (Unity Smart Merge)                     │
│ → Coordinate who works on which scenes                      │
│ → Use scene additivity                                      │
└─────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────┐
│ PROBLEM: Repository growing too large                       │
├─────────────────────────────────────────────────────────────┤
│ SOLUTIONS:                                                   │
│ → Configure Git LFS properly                                │
│ → Clean up old branches                                     │
│ → Don't commit generated files (Library/)                   │
│ → Use .gitignore templates for game engines                │
└─────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────┐
│ PROBLEM: Builds breaking frequently                         │
├─────────────────────────────────────────────────────────────┤
│ SOLUTIONS:                                                   │
│ → Add CI build on every PR                                  │
│ → Implement smoke tests                                     │
│ → Require passing builds before merge                       │
│ → Add pre-commit hooks for validation                       │
└─────────────────────────────────────────────────────────────┘

Essential .gitignore

# Unity
Library/
Temp/
Obj/
Build/
*.csproj
*.unityproj
*.sln

# Unreal
Intermediate/
Saved/
DerivedDataCache/
*.sln

# Common
*.log
*.tmp
.DS_Store
Thumbs.db

Use this skill: When setting up pipelines, managing assets, or automating builds.

FAQ

What does the game-tools-workflows skill do?

Game development tools, asset pipelines, version control, build systems, and team development workflows for efficient production.

How do I install game-tools-workflows?

Run npx skills add https://github.com/pluginagentmarketplace/custom-plugin-game-developer --skill game-tools-workflows in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/game-tools-workflows/ (personal) or .claude/skills/game-tools-workflows/ (project).

Which AI agents can use game-tools-workflows?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is game-tools-workflows safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains game-tools-workflows?

It is published by pluginagentmarketplace in pluginagentmarketplace/custom-plugin-game-developer. It has 105 recorded installs.

More from pluginagentmarketplace/custom-plugin-game-developer

View all →

game-design-theory

pluginagentmarketplace/custom-plugin-game-developer

Comprehensive game design theory covering MDA framework, player psychology, balance principles, and progression systems. Master why games are fun.

Media & Creative2.5K installs

level-design

pluginagentmarketplace/custom-plugin-game-developer

Level design fundamentals, pacing, difficulty progression, environmental storytelling, and spatial design for engaging gameplay experiences.

Media & Creative565 installs

gameplay-mechanics

pluginagentmarketplace/custom-plugin-game-developer

Open the skill to read its SKILL.md instructions.

Media & Creative300 installs

daw-music

pluginagentmarketplace/custom-plugin-game-developer

Open the skill to read its SKILL.md instructions.

Media & Creative213 installs

game-engines

pluginagentmarketplace/custom-plugin-game-developer

Open the skill to read its SKILL.md instructions.

Media & Creative201 installs

particle-systems

pluginagentmarketplace/custom-plugin-game-developer

Open the skill to read its SKILL.md instructions.

Media & Creative177 installs

Popular media & creative skills

View category →

hyperframes

heygen-com/hyperframes

Read first to make, edit, animate or render any video with HyperFrames (HTML rendered to video), including launch films, explainers, music videos, charts, maps, vertical clips, title cards, captions and overlays. Holds the render contract, the work loop and what each kind of video needs.

Media & Creative1.2M installs

media-use

heygen-com/hyperframes

Get or make any media for a HyperFrames video - music, sound effects, images, icons, logos, voiceover, avatar and generated video, transcripts, cutouts, colour grades and looks - with HeyGen or free local tools, and mix placed audio. Also for footage that looks dark, flat or dull, or should be stylized or hidden.

Media & Creative1.1M installs

hyperframes-registry

heygen-com/hyperframes

About 450 ready-made HyperFrames blocks and components installed as editable source - transitions, overlays, titles, kinetic type, captions, charts, map overlays, 3D, camera moves. Use it before hand-building any named visual (CRT scanlines, glitch, film grain, a chart); also for hyperframes add and catalog.

Media & Creative1M installs

hyperframes-creative

heygen-com/hyperframes

Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use hyperframes-animation.

Media & Creative916.5K installs

ai-video-generation

101-skills/superpowers

Generate AI videos with Google Veo, Seedance 2.0, HappyHorse, Wan, Grok and 40+ models via inference.sh CLI. Models: Veo 3.1, Veo 3, Seedance 2.0, HappyHorse 1.0, Wan 2.5, Grok Imagine Video, OmniHuman, Fabric, HunyuanVideo. Capabilities: text-to-video, image-to-video, reference-to-video, video editing, lipsync, avatar animation, video upscaling, foley sound. Use for: social media videos, marketing content, explainer videos, product demos, AI avatars. Triggers: video generation, ai video, text to video, image to video, veo, animate image, video from image, ai animation, video generator, generate video, t2v, i2v, ai video maker, create video with ai, runway alternative, pika alternative, sora alternative, kling alternative, seedance, happyhorse

Media & Creative881.5K installs

ai-image-generation

101-skills/superpowers

Generate AI images with GPT-Image-2, FLUX, Gemini, Grok, Seedream, Reve and 50+ models via inference.sh CLI. Models: GPT-Image-2, FLUX Dev LoRA, FLUX.2 Klein LoRA, Gemini 3 Pro Image, Grok Imagine, Seedream 4.5, Reve, ImagineArt. Capabilities: text-to-image, image-to-image, inpainting, LoRA, image editing, upscaling, text rendering. Use for: AI art, product mockups, concept art, social media graphics, marketing visuals, illustrations. Triggers: flux, image generation, ai image, text to image, stable diffusion, generate image, ai art, midjourney alternative, dall-e alternative, text2img, t2i, image generator, ai picture, create image with ai, generative ai, ai illustration, grok image, gemini image, gpt image, openai image, chatgpt image

Media & Creative880.3K installs