菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | mcp-server-workflows |
| description | 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 an agent is changing the MCP workspace or agent-facing tool APIs.
The MCP target state is a clean automation layer for AI agents building and maintaining GameMaker games:
This skill appears once even if requested more than once; one broad MCP workflow skill covers the duplicated request.
MCP owns:
MCP does not own:
Domain behavior belongs in the owning workspace. MCP should expose it, not reimplement it.
Before editing an MCP tool:
Implementation should:
MCP tools should help agents act correctly with limited context.
Tool boundaries should match repository ownership.
Add or update tests for:
Before finishing MCP work, verify:
require(), any, or non-null assertions to bypass typing.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.