GMLoop

Create and modify GameMaker resources through structured project tooling. Use when working with objects, events, rooms, scripts, instances, project metadata, or resource relationships.

Use this skill to remove compatibility shims, legacy behavior wrappers, and import/export pass-through files by migrating call sites to direct ownership APIs.

Organize GameMaker resources, manage layout and naming, structure project notes, and establish reusable architectural systems. Use when organizing resources, naming systems, or structuring GameMaker projects.

Use Playwright to inspect, navigate, and play a running browser-based GameMaker game. Use when the user wants the agent to verify gameplay, menus, input, screenshots, browser behavior, or the exported HTML5 game loop. This skill is for operating the game through the browser like a player, not for editing code.

Understand and work with GameMaker Language (GML), including its syntax differences from JavaScript, GML-specific language constructs, data accessors, keywords, constants, and formatting conventions.

Apply adversarial verification during any meaningful code change before the approach hardens. Use for medium or larger changes where regressions, hidden coupling, ownership mistakes, or invalid assumptions are plausible. Skip only for trivial mechanical edits.

Apply adversarial verification during any meaningful code change before the approach hardens. Use for medium or larger changes where regressions, hidden coupling, ownership mistakes, or invalid assumptions are plausible. Skip only for trivial mechanical edits.

Use whenever code navigation, analysis, refactoring, or diagnostics are needed on a project that has a Language Server Protocol implementation. Covers all 29 lsp_* MCP tools exposed by lsp-mcp-server (TypeScript, Python, Rust, Go, C/C++, Ruby, PHP, Elixir, Kotlin, Java, and any user-configured language). Use it instead of grep/find/Read for ANY task that touches definitions, references, types, hover docs, completions, diagnostics, rename, code actions, call/type hierarchy, document/workspace symbols, document highlights, inlay hints, selection ranges, folding ranges, or batch file indexing.

Use GMLoop's MCP and CLI capabilities to inspect, parse, recover, refactor, lint, format, validate, and understand a GameMaker project. Use when changing GML code, configuring gmloop.json, choosing a GMLoop workflow, or investigating project symbols and relationships.

Diagnose GameMaker gameplay, resource, build, and runtime failures from reproducible evidence. Use when the game behaves incorrectly, fails validation, or cannot build or run.

Define and maintain a focused game design, core loop, player verbs, goals, progression, feedback, accessibility, and minimum playable scope. Use when planning or changing the direction of a GameMaker game.

Improve game feel through readable feedback, animation, audio, timing, camera, particles, transitions, and accessibility without obscuring the core loop. Use after gameplay behavior is stable.

Implement gameplay systems in idiomatic GameMaker Language using clear object events, scripts, state machines, input, collisions, rooms, persistence, and performance practices. Use for gameplay code and runtime behavior.

Design deterministic tests for GML gameplay, scripts, resources, and runtime behavior. Use when adding features, fixing regressions, or validating an Auto-Game build.

Turn a GameMaker prototype into a coherent, playable vertical slice with bounded content, integrated systems, tests, and polish. Use when advancing from isolated mechanics to a complete representative experience.

Simplifies code for clarity while preserving behavior. Use when code works but is harder to read, maintain, or extend than it should be, especially in this TypeScript + GML monorepo.

Use this skill when building or modifying the GMLoop UI under src/ui. The UI stack is Lit + TypeScript with light-DOM rendering only.

Use this skill when working on GML ESLint language support, lint rules, diagnostics, single-file autofixes, rule tests, parser services, or formatter/lint/refactor boundaries.

Use this skill when working on the GML formatter or Prettier plugin, including printing, layout, comment placement, formatting options, formatter tests, or formatter/linter ownership boundaries.

Use this skill when working on project-wide refactors, codemods, rename transactions, workspace edits, metadata updates, codemod safety, or refactor CLI behavior.

Resolve merge, rebase, cherry-pick, formatter, generated-file, and commit-history conflicts safely while minimizing unrelated churn.

Use this skill when working on CLI commands, command routing, watch mode, project path handling, telemetry, command tests, or exposing repository tooling through the CLI.

Use this skill when working on shared core AST types, node metadata, traversal, structural helpers, cloning, equality, path utilities, or public core API boundaries.

Use this skill when working on MCP server tools, tool schemas, AI-agent workflow APIs, structured tool outputs, or exposing GMLoop capabilities to external agents.

Use this skill when working on the GML parser workspace, ANTLR grammar, tokenization, parse errors, AST construction, source locations, or strict GameMaker Language syntax adherence.

Use this skill when improving performance, memory use, streaming architecture, large-project indexing, codemod throughput, watch-mode responsiveness, or performance test failures.

Use this skill when working on semantic analysis, scope tracking, symbol resolution, SCIP modeling, graph/search/context retrieval, or project index storage and query behavior.

Use this skill when working on GML-to-JavaScript transpilation, runtime wrapper injection, hot reload patches, symbol dispatch, browser runtime integration, or live GameMaker execution behavior.

Use this skill when changing workspace public APIs, package boundaries, index exports, inter-workspace imports, dependency ownership, module structure, or architectural responsibility splits.