Game Tools Workflows

What it does

This skill automates complex game development tasks by creating and executing custom workflows. It streamlines asset management, repetitive processes, and enforces best practices across a wide range of tools commonly used in game development including Unity, Unreal Engine, Godot, Visual Studio, Blender, Maya, Wwise, FMOD, Jira, Notion, Slack, Discord, and more. The skill facilitates consistent Git branching strategies, LFS configuration, commit message formatting, and build automation processes.

When to use it

• To enforce a standardized Git workflow for game development teams using branches like main, develop, feature/*, fix/*, and release/*.
• When needing to automate repetitive tasks such as building game projects across different platforms (e.g., Windows, macOS, Linux).
• For ensuring consistent commit message formatting with prefixes like feat, fix, art, audio, etc.
• To manage large asset files using Git LFS for common file types like PSD, FBX, WAV, MP3, PNG, TGA and ZIP.

Key capabilities

• Git Workflow Automation: Enforces branching strategies (main, develop, feature/, fix/, release/*).
• LFS Configuration: Automates Git LFS configuration for common game asset file types.
• Commit Convention Enforcement: Ensures commit messages follow a specific format with defined prefixes.
• Build Automation: Executes build scripts using Unity (and potentially other engines) in batch mode, generating builds with version numbers.

Example prompts

• "Create a Git branch named 'feature/new-character' for developing a new character."
• "Run the build script for Windows in release configuration."
• "Enforce commit message formatting using prefixes like 'feat', 'fix', or 'art'."
• “Configure Git LFS to track .psd files.”

Tips & gotchas

• The skill requires familiarity with common game development tools and workflows.
• Build automation relies on a pre-existing build script, as demonstrated in the provided example using Unity. The path to your Unity installation is required for building.
• This skill focuses on automating processes within a defined tool stack; it does not provide direct integration with all possible game development software.