菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | gmloop-prototype-to-vertical-slice |
| description | 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. |
Define the shortest complete player journey that demonstrates the intended game from launch through a meaningful outcome. Use the existing prototype as evidence: preserve mechanics that serve the core loop and remove or defer disconnected experiments.
The slice should include:
gmloop-game-design for conceptual signals and gmloop-game-polish-and-juice for the polish pass).gmloop-gml-tests for standard test layer definitions).Write acceptance criteria before expanding implementation. Every task should connect to a slice criterion or remove a blocker to proving one.
gmloop-game-polish-and-juice).Defer content breadth, alternate modes, generalized frameworks, speculative extensibility, and progression that the representative journey does not exercise.
Run the slice from a clean project state. Confirm no manual editor repair is required, all referenced resources resolve, the intended target builds and launches, and the player can reach success and failure through normal input.
Record known limitations separately from required acceptance criteria. Finish with the exact verification performed and the next highest-value task, not a broad backlog of optional features.
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.