AlterLab-IEU

Invoke when the user asks about creative vision, game pillars, core fantasy, design direction, art style decisions, scope arbitration, or creative conflicts. Triggers on: "vision", "pillars", "creative direction", "core fantasy", "tone", "aesthetic", "creative conflict". Do NOT invoke for mechanics design (use game-designer) or technical architecture (use game-technical-director). Part of the Alte

Invoke when the user asks about story structure, branching narrative, dialogue systems, world-building, character design, environmental storytelling, ludonarrative coherence, writing for games, lore, theme, or character arcs. Triggers on: "story", "narrative", "dialogue", "lore", "world-building", "character arc", "branching", "ludonarrative". Do NOT invoke for creative vision (use game-creative-d

Invoke when the user asks about game economy, currency design, monetization, virtual currency, inflation, sink/source balance, F2P economy, premium currency, loot boxes, season pass, battle pass economics, dual currency, or resource flow modeling. Triggers on: "economy", "currency", "monetization", "F2P", "premium", "loot box", "battle pass", "sink/source", "inflation", "resource flow". Do NOT inv

Invoke when the user asks about game UI, onboarding, HUD design, controller navigation, player feedback, usability testing, colorblind modes, or game-specific UX patterns. Triggers on: "UI", "UX", "onboarding", "HUD", "controller nav", "usability", "colorblind", "player feedback", "menu design". Do NOT invoke for deep accessibility audits (use game-accessibility-specialist) or art style (use game-

Invoke when the user asks about sound design, music direction, audio identity, adaptive audio, spatial audio, SFX, sonic palette, dialogue systems, audio middleware, dynamic music, or sound bible creation. Triggers on: "sound design", "music", "audio", "SFX", "adaptive audio", "spatial audio", "sonic palette", "FMOD", "Wwise", "sound bible". Do NOT invoke for narrative dialogue writing (use game-n

Invoke when the user works with Unreal Engine 5 or asks about C++/Blueprints, GAS, replication, Nanite, Lumen, CommonUI, Enhanced Input, or World Partition. Triggers on: "Unreal", "UE5", "Blueprint", "GAS", "Nanite", "Lumen", "CommonUI", "Enhanced Input", "World Partition", ".uproject". Do NOT invoke for engine-agnostic architecture (use game-technical-director) or Godot/Unity questions. Part of t

Invoke when the user wants to brainstorm game ideas, explore concepts, run structured ideation, or develop a new game concept from scratch. Triggers on: "game idea", "brainstorm", "concept", "ideation", "what if", "game concept", "pitch". Do NOT invoke for reviewing existing designs (use game-design-review) or market analysis (use game-market-research). Part of the AlterLab GameForge collection.

Invoke to set up CI/CD pipelines for game builds -- automated testing, build pipelines, and deployment to Steam, itch.io, or Epic. Triggers on: "CI", "CD", "pipeline", "automated build", "deploy", "Steam deploy", "itch.io butler", "GitHub Actions game", "build automation". Do NOT invoke for general code review (use game-code-review) or manual testing guidance (use game-qa-lead). Part of the AlterL

Invoke when the user asks about art style, visual language, style guide, character design, environment art, UI art direction, asset pipeline, reference boards, color palette, or shape language. Triggers on: "art style", "visual", "style guide", "character design", "environment art", "asset pipeline", "color palette", "shape language". Do NOT invoke for UI/UX layout (use game-ux-designer) or creati

Invoke when the user asks about sprint planning, milestone tracking, scope management, risk assessment, scheduling, resource allocation, team velocity, or needs production coordination across the development team. Triggers on: "sprint", "milestone", "scope", "risk", "schedule", "resource", "velocity", "deadline", "crunch", "cut list". Do NOT invoke for creative vision (use game-creative-director)

Invoke when the user asks about accessibility, inclusive design, colorblind mode, remappable controls, screen reader support, EAA compliance, CVAA, difficulty options, motor accommodations, or one-handed mode. Triggers on: "accessibility", "inclusive design", "colorblind", "remappable controls", "screen reader", "EAA", "CVAA", "difficulty options", "motor accommodation", "one-handed". Do NOT invok

Invoke when the user asks about game mechanics, core loop, balance, progression, economy design, reward systems, onboarding, game feel, systems design, or GDD authoring. Triggers on: "mechanics", "core loop", "balance", "progression", "reward", "onboarding", "game feel", "systems design", "GDD". Do NOT invoke for creative vision (use game-creative-director) or economy monetization (use game-econom

Invoke when the user asks about testing strategy, bug tracking, playtest methodology, regression testing, release certification, QA automation, or bug triage. Triggers on: "testing", "bug", "QA", "regression", "certification", "playtest methodology", "test plan", "release gate". Do NOT invoke for usability testing (use game-ux-designer) or balance validation (use game-balance-check). Part of the A

Invoke when the user asks about game architecture, engine selection, performance budgets, technical debt, build pipeline, cross-platform, rendering pipeline, or CI/CD for games. Triggers on: "architecture", "engine selection", "performance budget", "tech debt", "build pipeline", "cross-platform", "rendering", "CI/CD". Do NOT invoke for creative vision (use game-creative-director) or engine-specifi

Invoke when the user works with Unity or asks about C#, MonoBehaviour, DOTS/ECS, Shader Graph, Addressables, UI Toolkit, URP/HDRP, or ScriptableObjects. Triggers on: "Unity", "MonoBehaviour", "DOTS", "ECS", "Shader Graph", "Addressables", "UI Toolkit", "URP", "HDRP", "ScriptableObject", ".unity", ".cs". Do NOT invoke for engine-agnostic architecture (use game-technical-director) or Godot/Unreal qu

Invoke when the user wants a game-specific code review, architecture check, or technical analysis of game code. Covers frame independence, hot path performance, state machine integrity, and resource lifecycle. Triggers on: "code review", "review my code", "check architecture", "game code quality". Do NOT invoke for design document review (use game-design-review) or general sprint planning (use gam

Invoke when the user works with Godot Engine or asks about GDScript, scene composition, signals, resources, shaders, GDExtension, physics, or Godot UI. Triggers on: "Godot", "GDScript", "scene tree", "signals", ".tscn", ".tres", "GDExtension", "project.godot". Do NOT invoke for engine-agnostic architecture (use game-technical-director) or Unity/Unreal questions (use the appropriate engine speciali

Invoke for guided game design document authoring -- section-by-section GDD creation with validation, pillar alignment, and scope tier marking. Triggers on: "write GDD", "create GDD", "game design document", "document my game", "GDD authoring", "fill in GDD". Do NOT invoke for reviewing an existing GDD (use game-design-review) or designing specific game systems (use game-designer). Part of the Alte

Invoke for game jam participation -- 48-72 hour compressed development workflow. Triggers on: "game jam", "jam mode", "Ludum Dare", "GMTK Jam", "Global Game Jam", "Brackeys Jam", "48 hours", "jam submission". Do NOT invoke for normal development timelines (use game-start). Part of the AlterLab GameForge collection.

Conduct market research for a game concept -- competitive landscape, market sizing, audience analysis, trend detection, and positioning strategy. Triggers on: "market research", "competitive analysis", "market sizing", "audience analysis", "is this game viable", "similar games", "market validation". Do NOT invoke for brainstorming ideas (use game-brainstorm) or economy monetization design (use gam

Invoke when the user is preparing for game release, needs a launch checklist, store submission guidance, go/no-go decision framework, or day-one patch planning. Covers Steam, itch.io, Epic, and console submission pipelines. Triggers on: "launch", "release", "store submission", "go/no-go", "day-one patch", "launch readiness". Do NOT invoke for sprint planning (use game-sprint-plan) or code review (

Invoke when the user wants feedback on a game design document, GDD review, design evaluation, or consistency check on an existing design. Triggers on: "review my GDD", "design feedback", "evaluate design", "design document review", "GDD critique". Do NOT invoke for brainstorming new ideas (use game-brainstorm) or balance tuning (use game-balance-check). Part of the AlterLab GameForge collection.

Coordinate multiple agents on complex game development features using battle-tested spawn recipes. Triggers on: "multi-agent coordination", "team orchestration", "feature handoff", "cross-domain collaboration", or when a task spans multiple specialist domains (combat system, narrative feature, UI overhaul, performance pass, launch prep). Do NOT invoke for single-domain tasks -- route directly to t

Invoke when the user wants to plan, execute, or analyze a structured playtest session with behavioral observation. Covers protocol design, observer guides, and data synthesis. Triggers on: "playtest", "player feedback", "usability test", "observation session", "playtest analysis". Do NOT invoke for QA bug testing (use game-qa-lead) or balance tuning (use game-balance-check). Part of the AlterLab G

Invoke when the user needs to plan a development sprint, break down tasks, schedule game work, or organize a sprint with cross-discipline dependencies. Triggers on: "sprint plan", "task breakdown", "development planning", "scheduling", "sprint backlog". Do NOT invoke for scope evaluation (use game-scope-check) or retrospectives (use game-retrospective). Part of the AlterLab GameForge collection.

Invoke when the user wants to start a new game project, set up project scaffolding, onboard into an existing codebase, or initialize GameForge session state. Triggers on: "start a game", "new game project", "set up project", "project onboarding", "initialize project". Do NOT invoke for brainstorming ideas (use game-brainstorm) or prototyping mechanics (use game-prototype). Part of the AlterLab Gam

Utilize para validar o balanceamento de jogos, ajustar sistemas de economia, analisar curvas de progressão, avaliar a escala de dificuldade e verificar o ritmo das recompensas, incluindo simulação Monte Carlo e validação estatística.

Esta skill realiza post-mortems estruturados para analisar os resultados do projeto, identificar lições e coletar dados relevantes automaticamente. Ela é acionada na conclusão do projeto ou por palavras-chave específicas, excluindo retrospectivas de sprint e revisões de design.

Invoque quando o usuário deseja prototipar rapidamente uma mecânica, testar uma prova de conceito, realizar desenvolvimento guiado por hipóteses ou validar uma ideia de jogo antes da produção completa.

Avalia o escopo do projeto em relação ao cronograma e recursos, sendo útil para gerenciar o scope creep, listas de funcionalidades e restrições de recursos. Não deve ser usada para planejamento de sprints ou status geral do projeto.

Esta skill lida com perguntas sobre localização, tradução, i18n, internacionalização, extração de strings, adaptação cultural, texto RTL/CJK e preparação EFIGS. Não a utilize para escrita narrativa ou acessibilidade.

Realize uma análise pós-mortem de desenvolvimento de jogos, seguindo a tradição da GDC. Esta skill é ativada por termos como "retrospectiva" ou "lições aprendidas", mas não para revisão de documentos de design ou playtesting.

Gera documentação a partir de código ou protótipos existentes, acionado por frases como 'documentar isso' ou 'gerar docs do código'. Não utilize para novos documentos de design do zero.

Acionar quando o usuário precisar configurar análises, definir eventos de telemetria, estabelecer KPIs, construir painéis, configurar testes A/B ou implementar recursos de design baseado em dados.