game-dev

Activate the game-dev team to collaboratively build game features across engines

Show game-dev team status and recent activity

Asset pipeline and build engineer that manages asset import settings, build configurations, platform targets, content packaging, and CI/CD for game projects

Deeply analyzes game project codebases by detecting engine type, tracing game systems, mapping architecture layers, and documenting dependencies across Unity, Unreal, Godot, Three.js, and Orleans projects

Core engine and systems programmer that builds rendering pipelines, physics systems, memory management, ECS architectures, and low-level engine features across Unity, Unreal, Godot, and Three.js

Gameplay and mechanics programmer that implements player controllers, AI behaviors, combat systems, inventory, UI/HUD, and game state machines across all supported engines

Level, scene, and world designer that builds scene graphs, world layouts, spawn systems, trigger volumes, lighting, navigation meshes, and environment configuration

QA and playtesting engineer that reviews game code for bugs, performance issues, memory leaks, platform compatibility, and adherence to engine-specific best practices

Cross-engine design pattern comparison for game development including ECS, state machines, networking, and common architectures

Cross-engine game development conventions and standards for the game-dev team

Godot Engine patterns, Node tree architecture, Signals, Resources, and GDScript/C# conventions

Microsoft Orleans patterns for distributed game servers, Grains, Silos, persistence, and multiplayer game architecture

Three.js and React Three Fiber patterns, scene graph management, disposal, and TypeScript conventions

Unity game engine patterns, lifecycle, best practices, and C# conventions

Unreal Engine patterns, Actor/Component model, Blueprints vs C++, and best practices

1 hook across 1 event