菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | gmloop-game-polish-and-juice |
| description | 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. |
Polish only after the underlying gameplay transition is correct and reproducible. Establish the intended player information before adding effects.
Prioritize feedback in this order:
Combine animation, timing, camera, particles, audio, UI, and transitions only when each channel contributes useful information. Use restrained anticipation, impact, recovery, and cooldown timing so effects reinforce gameplay state.
Compare the same gameplay moment before and after polish. Verify that a player can identify the action, consequence, source of danger, and next available decision more quickly or reliably.
Exercise repeated events, simultaneous effects, low frame rate, pause, room transition, restart, success, and failure. Confirm effects clean up and do not accumulate persistent instances, audio, alarms, or camera state.
Report the gameplay signals improved, accessibility/performance constraints considered, and runtime checks performed.
