القائمة
Tells container agents where the Unreal Engine source tree is mounted inside the container, so they can grep and read engine headers to verify API signatures and class hierarchies.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use for any container agent that posts progress to the coordination server's message board. Defines the curl format, channels, message types, payload conventions, posting responsibilities, and verbosity levels.
Use when a review agent must produce structured output. Defines the BLOCKING/NOTE/Summary/Verdict template, the two-tier confidence rubric, and the JSON shadow block consumed by POST /tasks/:id/reviews. Compose with review-process and a domain skill.
Use when an agent evaluates the output of other agents or decides whether work meets the bar. Enforces rigorous quality standards — reject shortcuts, demand evidence, no rubber-stamping.
Use when an agent is the FSM arbitrator on a durable task. Defines the two triggers, the three ruling types, the POST contract, the addendum-file rules for contradiction rulings, and the 409 handling. Project-agnostic.
Use when an agent must review code changes. Defines the universal review sequence — identify files, read context, check against domain criteria, score, filter. Compose with a domain skill and review-output-schema.
Use when an agent must write code via test-driven development. Defines the types-stubs-red-green-refactor cycle with build verification. The last action before finishing must be a successful build with all tests passing.
| name | ue-engine-mount |
| description | Tells container agents where the Unreal Engine source tree is mounted inside the container, so they can grep and read engine headers to verify API signatures and class hierarchies. |
| axis | environment |
The Unreal Engine 5.7 source tree is mounted read-only inside the container at:
/engine
This is the same content as <UE install>/Engine on the host. Use it whenever you need to verify a UE API, check a class hierarchy, find a function signature, or look up usage examples — Read, Glob, and Grep all work against /engine exactly as they do against /workspace.
Common entry points:
/engine/Source/Runtime/ — runtime modules (Core, CoreUObject, Engine, etc.)/engine/Source/Editor/ — editor-only modules/engine/Source/Developer/ — developer tooling/engine/Plugins/ — engine-bundled pluginsDo not attempt to write to /engine — the mount is read-only and any modification attempt will fail.
Project-side plugins configured for this project (e.g. Voxel, UE5Coro, SubsystemBrowserPlugin) are mounted read-only at:
/plugins-ro/<plugin-name>
Use this path for any read of plugin source — Read, Glob, Grep all work. They are not symlinked into /workspace/Plugins/, so anything you see at that path in the working tree is repo content, not a host mount.