Role Java Engineer
Java code review: modern Java (14+), records, sealed classes, immutability, JUnit 5 + AssertJ patterns, and Spring Boot conventions. Use when reviewing or writing Java code.
Role Game Balance Designer
Combat and progression balance: stat budgets, TTK/DPS, power curves, difficulty scaling, and competitive fairness. Use when tuning numbers that determine pacing, challenge, and power growth.
Lead Producer
Top-level orchestrator for multi-domain tasks. Routes work to specialist roles, enforces simplification, stress-tests via Devil's Advocate before acceptance.
Role Security Engineer
Security review: threat modeling, attack-surface analysis, auth/authz audit, supply-chain risk, and exploit prioritization. Use for pre-release security assessment or vulnerability review.
Team Infrastructure
Infrastructure team: deployment safety, capacity, observability, platform setup, and data-operational risk in one production-readiness assessment.
Role Kotlin Engineer
Kotlin code review: null safety, immutability, coroutine patterns, sealed types, and testing with Kotest/Turbine. Use when reviewing or writing Kotlin code.
Role Python Engineer
Python code review: PEP 8, type annotations, immutability patterns, pytest discipline, and async patterns. Use when reviewing or writing Python code.
Team Frontend Team
Frontend review team: UX quality, implementation health, accessibility, and frontend-backend integration in one recommendation. Use for UI features or frontend-heavy flows.
Role Economist
Monetary health analysis: money supply, inflation/deflation, wealth distribution, liquidity, and fiscal policy levers. Use when analyzing economic health metrics or recommending macro-level policy adjustments.
Role Railway Deployment
Railway.app deployment review: service topology, environment handling, scaling rules, persistence, observability, and platform cost. Use for Railway-specific deployment planning or auditing.
Role Narrative Designer
Narrative review: story structure, quests, characters, dialogue, lore coherence, and emotional beats. Use when evaluating whether the story lands and stays consistent — not whether the mechanics are fun or fair.
Role Community Developer
Community health: contributor onboarding, governance, communication, ecosystem extensibility, and participation barriers. Use when diagnosing why a community is stagnant or hard to join.
Role Software Architect
System architecture review: decomposition, service boundaries, contracts, migrations, and hard-to-reverse decisions. Use when designing systems or evaluating what becomes difficult to change later.
Role Backend Engineer
Backend systems review: APIs, database access, concurrency, caching, and failure handling. Use when investigating correctness risks, performance bottlenecks, or resilience gaps in server-side systems.
Role Devops Engineer
Infrastructure and operations review: CI/CD pipelines, monitoring, incident readiness, rollback paths, and deployment safety. Use when evaluating whether a system can ship and recover safely.
Role Liveops Engineer
Live-service operations: incident triage, hotfix decisions, rollback criteria, player-impact assessment, and degradation strategies. Use when something is broken in production or when designing incident readiness.
Role Unity Engineer
Unity / C# engine review: component architecture, MonoBehaviour lifecycle, ScriptableObjects, modern C# idioms, and GC/frame-budget performance. Use when reviewing or writing Unity game code or C#.
Team Blue Team
Verification team for cleanup and simplification work. Confirms behavior, contracts, and architecture truth still hold after code removal or collapse.
Role Context Manager
Context window management: persisting critical state, checkpointing, and preventing context degradation in long sessions. Trigger at ~60% context usage or before large tasks.
Role Qa Engineer
Test strategy, coverage analysis, regression risk, edge cases, and acceptance criteria. Use when deciding what to test, diagnosing flaky tests, or designing verification plans.
Role Move Sui Developer
Move and Sui smart contract review: object ownership, capability safety, access control, transaction shape, gas risk, and upgrade implications. Use for smart contract audit or on-chain feature design.
Role Code Reduction Engineer
Safe removal of dead, duplicate, or unnecessarily complex code. Use when the safest improvement is deletion or simplification without changing architecture truth or intended behavior.
Role Typescript Engineer
TypeScript/JavaScript code review: strict typing, type-level design, async correctness, module boundaries, and Vitest/Jest discipline. Use when reviewing or writing TypeScript or JavaScript code.
Role Product Marketing Manager
Go-to-market review: launch planning, market and competitive positioning, audience targeting, and campaign messaging strategy. Use when taking something that already exists to market — not defining brand identity or deciding whether to build it.
Role Rust Engineer
Rust code review: ownership, borrowing, error handling, trait design, async patterns, and testing. Use when reviewing or writing Rust code.
Role Technical Product Manager
Technical feasibility gating: dependency risk, rollout complexity, hidden costs, and scope cuts. Use when a product decision depends on technical feasibility or migration risk.
Role Cpp Engineer
C++ code review: modern standards (C++17/20/23), RAII, memory safety, value semantics, const correctness, and GoogleTest patterns. Use when reviewing or writing C++ code.
Role Cto
Strategic technology decisions: build-vs-buy, platform bets, vendor evaluation, TCO analysis, and organizational readiness. Use when technology direction must match business, team, and time horizon.
Role Godot Engineer
Godot 4 / GDScript engine review: scene-node architecture, signals and event buses, static typing, Resources, performance, and shaders/GDExtension. Use when reviewing or writing Godot game code.
Role Brand Strategist
Brand voice, positioning, visual rules, and cross-surface consistency. Use when defining or applying brand identity without turning into raw frontend implementation.
Team Dev Team
Technical review team: architecture, code quality, and test coverage in one unified assessment. Use for code review, design review, or implementation validation.
Role Economy Designer
Economy systems architecture: faucets, sinks, converters, resource flows, marketplace mechanics, and loop closure. Use when designing or reviewing structural mechanics that move value through a system.
Team Brand Team
Brand system team: tone, positioning, visual rules, and cross-surface identity standards. Use when defining or tightening brand consistency across product, docs, and community.
Team Architecture Review
Architecture review team: system design, migrations, hard-to-reverse decisions, with required Mermaid diagram. Use for new systems, major refactors, or technology choices.
Role Technical Writer
Documentation review and design: Diataxis taxonomy, audience analysis, API docs, ADRs, changelogs, and progressive disclosure. Use when documentation needs clarity, structure, and maintainability assessment.
Role Scalability Engineer
Scalability analysis: bottleneck identification, load profiling, capacity planning, and growth risk. Use when evaluating what breaks first at 10x or 100x scale.
Role Behavioral Economist
Player behavior prediction through cognitive bias analysis: loss aversion, anchoring, FOMO, sunk cost, framing effects. Use when predicting why players won't do the mathematically optimal thing.
Team Documentation
Documentation team: guides, API docs, ADRs, and knowledge-base work with scope control and audience fit.
Role Open Source Engineer
Open source readiness: license compliance, dependency hygiene, SBOM, release process, and public-code safety. Use when preparing code for public release or auditing supply-chain transparency.
Role Principal Software Engineer
Code quality, maintainability, abstraction health, and technical debt assessment. Use when reviewing whether code is understandable, changeable, and trustworthy for the next engineer.
Team Economy Team
Economy analysis team: flow design, monetary health, player behavior, exploit risk, and product impact synthesized. Use for economy design, reward systems, marketplace, or monetary policy review.
Role Level Designer
Level and content design review: spatial layout, encounter choreography, content sequencing, and moment-to-moment flow. Use when evaluating how a space or encounter is built — not the difficulty numbers or the global progression experience.
Role Ui Ux Designer
UX review: user flows, information architecture, interaction patterns, visual hierarchy, error recovery, and accessibility. Use when analyzing whether users can complete their goal with low cognitive load.
Role Frontend Engineer
Frontend systems review: components, state management, rendering performance, accessibility, bundle health, and network failure handling. Use when analyzing or designing frontend architecture.
Role Data Engineer
Data pipeline review: schema contracts, freshness SLAs, ETL reliability, storage scaling, and data quality. Use when data systems need reliability-focused assessment.
Role Database Engineer
Database review: schema design, query performance, indexing, migrations, and transactional integrity. Use when the database itself — not the pipeline or the service — is the risk.
Role Product Manager
Product evaluation: user value, prioritization, MVP scope, launch conditions, and success metrics. Use when assessing whether a feature is worth doing and how to know if the bet paid off.
Role Game Designer
Gameplay systems review: core loops, progression, onboarding, failure states, and player motivation. Use when evaluating whether a design is engaging, readable, and worth mastering.
Role Analytics Engineer
Metrics and measurement review: KPI definitions, telemetry instrumentation, A/B test design, dashboard hierarchy, and anomaly detection. Use when ensuring metrics are trustworthy enough for decisions.
Role Go Engineer
Go code review: idiomatic patterns, error handling, concurrency safety, interface design, and testing. Use when reviewing or writing Go code.