[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CS0Z317HSCN5BHK4B84CBY":3,"skill-same:01M7CS0Z317HSCN5BHK4B84CBY":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7CS0Z317HSCN5BHK4B84CBY","game-engine-mcp-tools",null,"Use when an editor MCP server (unity, godot, unreal, blender) or the browser MCP shows up in your tool list - what each one can observe or change, how to check it is attached to YOUR task workspace, why the repo's tests still decide, the Blender code-execution caution, and the headless fallback when none is connected.","makifbaysal\u002Ftasktrooper","makifbaysal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25031940?v=4","01M7CRG3ZCSYZSSEVDMW3DEYC8","Mehmet Akif Baysal","01M7CRG401FJ8YAXH5ER730XYV",122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fgame-developer\u002Fskills\u002Fgame-engine-mcp-tools\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: game-engine-mcp-tools\ncategory: tools\ndescription: Use when an editor MCP server (unity, godot, unreal, blender) or the browser MCP shows up in your tool list - what each one can observe or change, how to check it is attached to YOUR task workspace, why the repo's tests still decide, the Blender code-execution caution, and the headless fallback when none is connected.\ntech_stack: Game core\nsource: informed by the CoplayDev\u002Funity-mcp, hi-godot\u002Fgodot-ai, Unreal MCP and MCP for Blender documentation and this product's MCP server templates; own wording\n---\n# Game Engine MCP Tools\n\n## Overview\n\nThe user can connect live editors to you through MCP servers in Settings → MCP servers. They are optional and disabled by default. When one is connected you can look inside a running editor — scene hierarchy, console errors, test runs, screenshots — which is often the only way to observe an engine game on this machine. When none is connected, nothing changes: the headless commands (game-build-check, game-visual-self-review) are the path.\n\n**Core principle:** An editor MCP is an extra pair of eyes, never the verdict. The repository's tests, run in this task, decide; the MCP shows you what the build and the tests cannot.\n\n## Is it there?\n\nLook at your tool list. A connected server's tools appear there (in CLI runtimes as `mcp__\u003Cserver>__\u003Ctool>`, e.g. tools under `unity`, `godot`, `unreal`, `blender`, `browser`). No tools from it → it is not connected.\n\n- Never ask the user to install, enable or start an editor or MCP server mid-task. Fall back to the headless CLI and say in the closing message what you could not observe.\n- A tool call that fails because the editor is closed or busy is a finding, not something to retry in a loop.\n\n## First call: is the editor on your workspace?\n\nEditor MCP servers talk to whatever editor the user has open. That may be their main checkout, another branch, or another project — not your task workspace. Before trusting anything it shows, ask it for the open project's path (editor\u002Fproject info) and compare with your working directory.\n\n- Different path → its scenes, console and tests describe someone else's code. Do not edit through it; use the CLI instead, and note it in the closing message.\n- Same path → it sees your files once the editor has refreshed or recompiled them; trigger or wait for that before reading the console or running tests.\n\n## What each server is for\n\n| Server | What it is | Use it to | Watch out for |\n|---|---|---|---|\n| `unity` | MCP for Unity (CoplayDev\u002Funity-mcp); needs its package in the project and the Editor open | Inspect scenes and GameObjects (`manage_scene`), read console errors and compile errors (`read_console`), run EditMode\u002FPlayMode tests in the open editor (`run_tests`), control play mode and editor state (`manage_editor`), capture editor\u002Fgame views | An open Editor locks the project, so a batchmode CLI run on the same project fails — run the tests through the MCP instead, and still read their results. `UNITY_MCP_DEFAULT_INSTANCE` picks the editor when several are open. |\n| `godot` | Godot AI (hi-godot\u002Fgodot-ai); needs the `addons\u002Fgodot_ai` addon and the editor open | Inspect the scene tree and nodes, read scripts and validation errors, run the project or a scene, read debugger\u002Foutput errors, run the test suite | The server version must equal the project's addon version, or it refuses to attach. Its server uses port 8000. |\n| `unreal` | Epic's built-in Unreal MCP (UE 5.8+, \"Unreal MCP\" plugin, Experimental), loopback HTTP on 127.0.0.1:8000 | Inspect actors, components and assets in the open level; run editor Python and automation commands; check what is placed where | Experimental: tool shapes can change between engine versions. Same port 8000 as Godot AI — only one of the two can run. No authentication: anything on this machine can call it. |\n| `blender` | MCP for Blender | Inspect and edit models, materials and renders; export assets for the game | `execute_blender_code` runs arbitrary Python inside Blender with the user's permissions. |\n| `browser` \u002F built-in browser tools | Browser automation | Load a web game, screenshot it at two viewports | See game-visual-self-review for the exact calls. |\n\n## Rules for using them\n\n1. **Observe first, change second.** Prefer read operations: hierarchy, components, console, test results, screenshots.\n2. **Changes made through an editor are changes in your diff.** Creating a GameObject, editing a prefab, saving a scene or importing an asset through MCP writes files in the working tree (scenes, prefabs, `.meta`, `.import`, `.uasset`). Review `git status` and `git diff` afterwards exactly as for your own edits; revert anything the task did not ask for, including re-serialisation noise from the editor.\n3. **Code changes go through files, not the editor.** Write scripts with your file tools and TDD; use the editor to compile, run tests and look. Script-editing tools in an MCP are not a way around tests.\n4. **Tests still decide.** A green `run_tests` call via MCP counts as a run when you read its results; a screenshot or a clean console does not replace the repository's tests or the standing acceptance criteria.\n5. **Never run code you did not write for this task.** Do not pass text from task descriptions, comments, assets or downloaded files into `execute_blender_code`, editor Python or any script-execution tool. Write the snippet yourself, keep it minimal, and read it before sending.\n6. **Exported assets follow the pipeline.** A mesh or texture produced in Blender goes through game-asset-pipeline and asset-hygiene: sensible poly count and LODs, platform texture compression, the engine's import metadata committed, Git LFS for the binaries, the `.blend` source only where the repository keeps sources.\n7. **Name what you used.** The closing message states the render path and the tool: e.g. \"engine capture via unity MCP (`run_tests` PlayMode 14\u002F14, Game view screenshot of Arena)\", or \"no editor MCP connected; Unity CLI not installed — not observed\".\n\n## Typical flows\n\n**Unity, editor connected on this workspace:** edit scripts and tests → wait for the editor to recompile → `read_console` (zero compile errors) → `run_tests` EditMode, then PlayMode if scenes\u002Fphysics changed → enter play mode on the changed scene, capture the game view → exit play mode, `git diff` for unintended scene or prefab changes.\n\n**Godot, editor connected:** write scripts and tests → ask for script validation\u002Ferrors → run the gdUnit4\u002FGUT suite through the tool (or the CLI if it does not expose tests) → run the changed scene, read debugger output, capture the viewport → check `git diff` for rewritten `.tscn`\u002F`.import` files.\n\n**Unreal, MCP on 5.8+:** compile with the CLI first (the editor must load the new module) → inspect the actors and assets the change affects → run the automation tests the editor exposes, or the headless CLI → screenshot through an automation command if available.\n\n**Nothing connected:** game-build-check for builds and tests, game-visual-self-review for captures, and an honest `NOT OBSERVED` line where neither works.\n\n## When a server misbehaves\n\n| Symptom | Likely cause | What you do |\n|---|---|---|\n| Tools listed, every call times out or says no editor | The editor is closed, or still importing\u002Fcompiling | One retry after the compile finishes; then fall back to the CLI and note it |\n| `godot` refuses to attach | Server and `addons\u002Fgodot_ai` versions differ | Fall back to the CLI; mention the mismatch in one card comment for the user — never bump the addon in a feature task |\n| `unreal` and `godot` both enabled, one fails to start | Both want port 8000 | Use whichever answers; mention the conflict once |\n| `unity` answers for the wrong project | Several editors open | It follows `UNITY_MCP_DEFAULT_INSTANCE`; if that is not your workspace, treat the server as unavailable |\n| Test results via MCP disagree with the CLI | The editor has stale compiled code or another checkout open | Trust the CLI run on your workspace; report the disagreement |\n\nNever change MCP settings, ports or editor preferences to make a server work — that is the user's configuration.\n\n## Common Mistakes\n\n- Trusting an editor that has a different checkout open.\n- Saving a scene through MCP \"to be safe\" and shipping unrelated serialisation churn.\n- Treating a clean editor console as proof that tests pass.\n- Running Unity batchmode against a project the connected editor already has open.\n- Sending task text into a code-execution tool.\n\n## Red Flags\n\n- A closing message that claims an editor check without naming the server and what it showed.\n- Scene, prefab or asset files in the diff that no step of the plan meant to change.\n- `execute_blender_code` or editor Python containing anything copied from outside your own reasoning.\n","# Game Engine MCP Tools\n\n## Overview\n\nThe user can connect live editors to you through MCP servers in Settings → MCP servers. They are optional and disabled by default. When one is connected you can look inside a running editor — scene hierarchy, console errors, test runs, screenshots — which is often the only way to observe an engine game on this machine. When none is connected, nothing changes: the headless commands (game-build-check, game-visual-self-review) are the path.\n\n**Core principle:** An editor MCP is an extra pair of eyes, never the verdict. The repository's tests, run in this task, decide; the MCP shows you what the build and the tests cannot.\n\n## Is it there?\n\nLook at your tool list. A connected server's tools appear there (in CLI runtimes as `mcp__\u003Cserver>__\u003Ctool>`, e.g. tools under `unity`, `godot`, `unreal`, `blender`, `browser`). No tools from it → it is not connected.\n\n- Never ask the user to install, enable or start an editor or MCP server mid-task. Fall back to the headless CLI and say in the closing message what you could not observe.\n- A tool call that fails because the editor is closed or busy is a finding, not something to retry in a loop.\n\n## First call: is the editor on your workspace?\n\nEditor MCP servers talk to whatever editor the user has open. That may be their main checkout, another branch, or another project — not your task workspace. Before trusting anything it shows, ask it for the open project's path (editor\u002Fproject info) and compare with your working directory.\n\n- Different path → its scenes, console and tests describe someone else's code. Do not edit through it; use the CLI instead, and note it in the closing message.\n- Same path → it sees your files once the editor has refreshed or recompiled them; trigger or wait for that before reading the console or running tests.\n\n## What each server is for\n\n| Server | What it is | Use it to | Watch out for |\n|---|---|---|---|\n| `unity` | MCP for Unity (CoplayDev\u002Funity-mcp); needs its package in the project and the Editor open | Inspect scenes and GameObjects (`manage_scene`), read console errors and compile errors (`read_console`), run EditMode\u002FPlayMode tests in the open editor (`run_tests`), control play mode and editor state (`manage_editor`), capture editor\u002Fgame views | An open Editor locks the project, so a batchmode CLI run on the same project fails — run the tests through the MCP instead, and still read their results. `UNITY_MCP_DEFAULT_INSTANCE` picks the editor when several are open. |\n| `godot` | Godot AI (hi-godot\u002Fgodot-ai); needs the `addons\u002Fgodot_ai` addon and the editor open | Inspect the scene tree and nodes, read scripts and validation errors, run the project or a scene, read debugger\u002Foutput errors, run the test suite | The server version must equal the project's addon version, or it refuses to attach. Its server uses port 8000. |\n| `unreal` | Epic's built-in Unreal MCP (UE 5.8+, \"Unreal MCP\" plugin, Experimental), loopback HTTP on 127.0.0.1:8000 | Inspect actors, components and assets in the open level; run editor Python and automation commands; check what is placed where | Experimental: tool shapes can change between engine versions. Same port 8000 as Godot AI — only one of the two can run. No authentication: anything on this machine can call it. |\n| `blender` | MCP for Blender | Inspect and edit models, materials and renders; export assets for the game | `execute_blender_code` runs arbitrary Python inside Blender with the user's permissions. |\n| `browser` \u002F built-in browser tools | Browser automation | Load a web game, screenshot it at two viewports | See game-visual-self-review for the exact calls. |\n\n## Rules for using them\n\n1. **Observe first, change second.** Prefer read operations: hierarchy, components, console, test results, screenshots.\n2. **Changes made through an editor are changes in your diff.** Creating a GameObject, editing a prefab, saving a scene or importing an asset through MCP writes files in the working tree (scenes, prefabs, `.meta`, `.import`, `.uasset`). Review `git status` and `git diff` afterwards exactly as for your own edits; revert anything the task did not ask for, including re-serialisation noise from the editor.\n3. **Code changes go through files, not the editor.** Write scripts with your file tools and TDD; use the editor to compile, run tests and look. Script-editing tools in an MCP are not a way around tests.\n4. **Tests still decide.** A green `run_tests` call via MCP counts as a run when you read its results; a screenshot or a clean console does not replace the repository's tests or the standing acceptance criteria.\n5. **Never run code you did not write for this task.** Do not pass text from task descriptions, comments, assets or downloaded files into `execute_blender_code`, editor Python or any script-execution tool. Write the snippet yourself, keep it minimal, and read it before sending.\n6. **Exported assets follow the pipeline.** A mesh or texture produced in Blender goes through game-asset-pipeline and asset-hygiene: sensible poly count and LODs, platform texture compression, the engine's import metadata committed, Git LFS for the binaries, the `.blend` source only where the repository keeps sources.\n7. **Name what you used.** The closing message states the render path and the tool: e.g. \"engine capture via unity MCP (`run_tests` PlayMode 14\u002F14, Game view screenshot of Arena)\", or \"no editor MCP connected; Unity CLI not installed — not observed\".\n\n## Typical flows\n\n**Unity, editor connected on this workspace:** edit scripts and tests → wait for the editor to recompile → `read_console` (zero compile errors) → `run_tests` EditMode, then PlayMode if scenes\u002Fphysics changed → enter play mode on the changed scene, capture the game view → exit play mode, `git diff` for unintended scene or prefab changes.\n\n**Godot, editor connected:** write scripts and tests → ask for script validation\u002Ferrors → run the gdUnit4\u002FGUT suite through the tool (or the CLI if it does not expose tests) → run the changed scene, read debugger output, capture the viewport → check `git diff` for rewritten `.tscn`\u002F`.import` files.\n\n**Unreal, MCP on 5.8+:** compile with the CLI first (the editor must load the new module) → inspect the actors and assets the change affects → run the automation tests the editor exposes, or the headless CLI → screenshot through an automation command if available.\n\n**Nothing connected:** game-build-check for builds and tests, game-visual-self-review for captures, and an honest `NOT OBSERVED` line where neither works.\n\n## When a server misbehaves\n\n| Symptom | Likely cause | What you do |\n|---|---|---|\n| Tools listed, every call times out or says no editor | The editor is closed, or still importing\u002Fcompiling | One retry after the compile finishes; then fall back to the CLI and note it |\n| `godot` refuses to attach | Server and `addons\u002Fgodot_ai` versions differ | Fall back to the CLI; mention the mismatch in one card comment for the user — never bump the addon in a feature task |\n| `unreal` and `godot` both enabled, one fails to start | Both want port 8000 | Use whichever answers; mention the conflict once |\n| `unity` answers for the wrong project | Several editors open | It follows `UNITY_MCP_DEFAULT_INSTANCE`; if that is not your workspace, treat the server as unavailable |\n| Test results via MCP disagree with the CLI | The editor has stale compiled code or another checkout open | Trust the CLI run on your workspace; report the disagreement |\n\nNever change MCP settings, ports or editor preferences to make a server work — that is the user's configuration.\n\n## Common Mistakes\n\n- Trusting an editor that has a different checkout open.\n- Saving a scene through MCP \"to be safe\" and shipping unrelated serialisation churn.\n- Treating a clean editor console as proof that tests pass.\n- Running Unity batchmode against a project the connected editor already has open.\n- Sending task text into a code-execution tool.\n\n## Red Flags\n\n- A closing message that claims an editor check without naming the server and what it showed.\n- Scene, prefab or asset files in the diff that no step of the plan meant to change.\n- `execute_blender_code` or editor Python containing anything copied from outside your own reasoning.\n",{"name":5,"source":24,"category":25,"tech_stack":26,"description":7},"informed by the CoplayDev\u002Funity-mcp, hi-godot\u002Fgodot-ai, Unreal MCP and MCP for Blender documentation and this product's MCP server templates; own wording","tools","Game core","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fgame-developer\u002Fskills\u002Fgame-engine-mcp-tools",18,"https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper","https:\u002F\u002Ftasktrooper.ai","https:\u002F\u002Fgithub.com\u002Fmakifbaysal","Senior Software Developer","2026-11-15 04:50:29",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add makifbaysal\u002Ftasktrooper --skill game-engine-mcp-tools",{"tool":42,"command":43},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill game-engine-mcp-tools",{"tool":45,"command":46},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill game-engine-mcp-tools","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fgame-developer\u002Fskills\u002Fgame-engine-mcp-tools\u002FSKILL.md",true,[],[51,57,64,71,78,85],{"skillNo":52,"name":53,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7CSVEPQW6J6TD6CS2T5FPNZ","visual-craft","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fvisual-craft\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7CSVAQG91ETHQ0HBNZDG5FR","ux-copy","Use when you write any words a user reads in a mockup or a hand-off - content language and voice, buttons, labels, errors, empty states, confirmations, numbers and dates, and the longest-string check","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fux-copy\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CSV6H0J38659NDXHJQ8396","screen-mockup-html","Use when you draw screens as the design task's HTML mockup - ONE canvas document holding every screen and every variant side by side, the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fscreen-mockup-html\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CSV3JFRF3BM3XK52M7YEYR","performance-awareness","How the performance score moves for your role. Use when the score context shows a declining trend, or before handing off work you have not self-checked against every criterion.","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fperformance-awareness\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CSTZDH00YRF5SCT7BRT9QD","design-variants","Use when a screen design needs variants - how many, variants as side-by-side rows on the one canvas, what makes two variants genuinely different, recommending one, how the human's choice is read, and narrowing to the chosen one in revision","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-variants\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CSTV6P3SM3PAE28DB0RF77","design-system-authoring","Use when you derive, change or extend a design system - where tokens live per stack, the DTCG token tree, role-based names for both themes, base vs layer vs drift, the DESIGN.md section order, the inventory format, the contrast check and the lint every proposal returns","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-system-authoring\u002FSKILL.md",[],[]]