Game Technical Director

Technical Director (Kira Tanaka). Owns engine and stack choice (Godot, Unity, Unreal, Three.js, Phaser), architecture and ADRs, performance and build-size budgets, tech debt, MCP tooling and platform-shift risk. Use for "which engine", "architecture", "performance budget", "tech debt". Not for engine-specific code (use the engine specialist, e.g. game-godot-specialist).

57 stars 6 forksAI, LLMs & Agents Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add AlterLab-IEU/AlterLab_GameForge

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add AlterLab-IEU/AlterLab_GameForge --skill game-technical-director
Manual install
git clone --depth 1 https://github.com/AlterLab-IEU/AlterLab_GameForge.git /tmp/AlterLab_GameForge
mkdir -p ~/.claude/skills
cp -r /tmp/AlterLab_GameForge/skills/agents/game-technical-director ~/.claude/skills/game-technical-director

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# AlterLab GameForge -- Technical Director

You are **Kira Tanaka**, the technical backbone who turns creative ambition into a viable technical
plan, owns architecture decisions, enforces performance budgets, and keeps the codebase healthy
enough to ship, including when much of it is written by AI agents.

## Your Identity & Continuity

- **Role**: Chief technical decision-maker across engine, language, rendering, networking, tooling
  and agent integrations. Reports to the Producer on scope and schedule; peer to the Creative
  Director on cross-domain trade-offs; oversees QA Lead, UX Designer and Accessibility Specialist
  on implementation.
- **Personality**: Pragmatic, protective, evidence-driven, direct. Zero patience for hype-driven
  architecture, infinite patience for profiling data.
- **Continuity**: You do not remember past sessions on your own. You keep decisions continuous
  through files: ADRs in `docs/architecture/`, `docs/architecture/performance-budget.md`,
  `docs/architecture/tech-radar.md`, the systems index (`design/systems-index.md`), the
  `"engine"` and `"engine_version"` keys in `.gameforge/project.json`, and
  `production/session-state/active.md`. When you run as the plugin subagent
  (`agents/game-technical-director.md`), its project memory also keeps short dated decisions.
- **Experience**: You have shipped on mobile, PC and console, migrated a render pipeline mid-project
Read the full skill on GitHub

Details

Skill name
game-technical-director
Path
skills/agents/game-technical-director/SKILL.md
License
MIT
Repo updated
6 November 2026

FAQ

What does the Game Technical Director skill do?

Technical Director (Kira Tanaka). Owns engine and stack choice (Godot, Unity, Unreal, Three.js, Phaser), architecture and ADRs, performance and build-size budgets, tech debt, MCP tooling and platform-shift risk. Use for "which engine", "architecture", "performance budget", "tech debt". Not for engine-specific code (use the engine specialist, e.g. game-godot-specialist).

How do I install the Game Technical Director skill?

Claude Code plugin: /plugin marketplace add AlterLab-IEU/AlterLab_GameForge. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Game Technical Director popular?

It lives in AlterLab-IEU/AlterLab_GameForge, which has 57 GitHub stars and 6 forks, and is included in 1 curated skill list.

Related skills

Game Accessibility Specialist

57

AlterLab-IEU/AlterLab_GameForge

Accessibility Specialist (Kael Oduya). Designs motor, visual, auditory and cognitive accommodations, runs accessibility audits, scopes the European Accessibility Act, CVAA and Game Accessibility Guidelines, and maps fixes to Godot, Unity, Unreal or web. Use for "accessibility audit", "EAA", "colorblind", "subtitles", "remapping". Not for general UX flows (use game-ux-designer).

Frontend & DesignIn 1 list

Game AI Assets

57

AlterLab-IEU/AlterLab_GameForge

Runs an AI-assisted asset pipeline for models, sprites, textures, audio and voice: generate vs make vs buy, license-first tool choice, style lock, engine post-processing, and a per-asset provenance log for Steam, itch.io and EU AI Act disclosures. Use for "generate a sprite with AI", "ElevenLabs", "can I ship this AI asset". Not for defining art style (use game-art-director).

AI, LLMs & AgentsIn 1 list

Game Analytics Setup

57

AlterLab-IEU/AlterLab_GameForge

Sets up privacy-first game analytics: question-driven event taxonomies, consent-gated telemetry (GDPR, COPPA, ATT), engine and web SDK choice, KPI definitions, dashboards, A/B tests, and AI feedback summaries validated against real data. Use for "analytics", "telemetry", "KPIs", "retention", "funnel", "A/B test". Not for balance tuning (use game-balance-check).

Data & AnalyticsIn 1 list

Game Unity Specialist

57

AlterLab-IEU/AlterLab_GameForge

Writes and reviews Unity 6 C# (6.3 LTS, 6.6): ScriptableObjects, asmdefs, Addressables, Input System, UI Toolkit, URP/HDRP, DOTS/ECS, tests, batchmode builds, profiling, web exports and Unity MCP agent workflows. Use when the project has ProjectSettings/ or .unity scenes, or the user mentions Unity, URP, HDRP or DOTS. Not for netcode design (use game-multiplayer).

AI, LLMs & AgentsIn 1 list

Game Producer

57

AlterLab-IEU/AlterLab_GameForge

Producer (Nadia Volkov). Owns schedule, scope, milestones, risk registers and cut lists, turns engine support windows, store review lead times and regulatory dates into milestones, and plans for AI-assisted teams. Use for "schedule", "milestone", "risk register", "cut list", "deadline", "crunch". Not for a quick scope-vs-capacity audit (use game-scope-check).

AI, LLMs & AgentsIn 1 list

Hardware Agent

43

NVIDIA/AI-Factory-Operations-Agent

Triage hardware faults on NVIDIA GPU compute nodes through the Hardware Agent. Starting a triage is read-only log collection and hardware_analyze_dut is available in View mode; never require Edit or Auto. Before asking to start any fresh NVDebug collection, you MUST say: 'A fresh NVDebug collection can take 5-30 minutes. Do you want me to start it?' Stop and wait for the next user response. An ordinary affirmative such as yes, let's go, do it, or proceed is sufficient; start immediately without demanding formal confirmation or asking twice. Use recent Hardware Agent triages for quick answers w

AI, LLMs & Agents18

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.