القائمة
Create and modify GameMaker resources through structured project tooling. Use when working with objects, events, rooms, scripts, instances, project metadata, or resource relationships.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | gmloop-gamemaker-resources |
| description | Create and modify GameMaker resources through structured project tooling. Use when working with objects, events, rooms, scripts, instances, project metadata, or resource relationships. |
Use the available structured project, resource, object, room, script, refactor, and validation capabilities instead of editing GameMaker metadata as unstructured text. Inspect the active tool's capabilities before assuming an operation or payload shape.
.yyp and confirm the project root.Do not infer resource identities from filenames alone when structured project metadata is available.
Prefer the narrowest structured operation that owns the change. Keep resource creation, object-event additions or removals, parent-child inheritance changes, room-instance placement, and project metadata modifications inside the available project-tooling boundaries.
[!IMPORTANT] Do not use resource metadata operations to write or modify GML gameplay logic code. All GML scripting inside object events or scripts belongs to
gmloop-gml-gameplayandgmloop-tooling.
[!TIP] To generate placeholder sprite frame/layer image assets for the game, use the
gmloop_resource_create_imageMCP tool (or thegmloop resource create-imageCLI command). This lets you generate solid-color PNG files at specific dimensions and colors directly.
Preserve stable resource names and identifiers unless the task explicitly requires a rename. When renaming, use the project-wide refactor transaction so references and metadata change together.
Do not hand-edit .yyp, .yy, or resource ordering as generic JSON. Do not copy opaque resource metadata from another project without resolving its dependencies.
After mutation:
List every created, updated, renamed, or removed resource; the capability used; the important relationships verified; and any build/runtime validation that could not be completed.