game-tools-workflows
Game development tools, asset pipelines, version control, build systems, and team development workflows for efficient production.
What this skill does
# 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
```python
# ✅ 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 │
└─────────────────────────────────────────────────────────Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.