القائمة
How to use unity-mcp tools effectively — batch_execute for speed, read_console for verification, resource queries for project state, tool organization patterns.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
DOTween animation library — sequence composition, tween lifecycle, easing, kill strategies. CRITICAL: Always kill tweens in OnDestroy to prevent leaks and errors.
Dialogue tree patterns — ScriptableObject graph, node types (text, choice, condition, event), typewriter effect, localization-ready. Load when implementing NPC conversations.
Generic state machine patterns — IState interface, StateMachine<T>, game state management (menu/gameplay/pause), enemy AI states, hierarchical FSM. Load when implementing state-driven behavior.
2D platformer architecture — tight controls (coyote time, input buffer, variable jump), level design patterns, collectibles, checkpoints, hazards, boss patterns.
Unity physics — non-allocating queries, collision layers, FixedUpdate discipline, continuous collision detection, character controllers, joints.
How the atomic instinct learning system works — observations, distillation, confidence scoring, project vs global scope, and promotion/evolution workflows.
| name | unity-mcp-patterns |
| description | How to use unity-mcp tools effectively — batch_execute for speed, read_console for verification, resource queries for project state, tool organization patterns. |
| alwaysApply | true |
The unity-mcp server gives Claude Code direct control over the Unity Editor. These patterns ensure you use it efficiently and safely.
Individual MCP calls have network overhead. batch_execute bundles multiple operations into one call — 10-100x faster.
// BAD — 5 separate calls, 5 round trips
manage_gameobject → create Player
manage_components → add Rigidbody2D to Player
manage_components → add BoxCollider2D to Player
manage_components → add SpriteRenderer to Player
manage_components → configure Rigidbody2D
// GOOD — 1 batch call
batch_execute → [
create Player,
add Rigidbody2D,
add BoxCollider2D,
add SpriteRenderer,
configure Rigidbody2D
]
Always batch when doing 2+ operations.
After writing scripts, creating objects, or modifying components, always check the console:
1. Write/Edit C# file
2. read_console → check for compilation errors
3. If errors: fix and repeat
4. Continue with MCP operations
5. read_console → check for runtime warnings
The console is your feedback loop. Don't assume operations succeeded.
Before making decisions about the project, read its state:
project_info resource → Unity version, platform, render pipeline
Don't assume:
| Task | Tool | Key Actions |
|---|---|---|
| Create/load/save scene | manage_scene | create, load, save, validate |
| Create/modify GameObjects | manage_gameobject | create, modify, delete, find |
| Add/configure components | manage_components | add, remove, configure, get |
| Physics setup | manage_physics | settings, layers, materials, joints |
| Camera/Cinemachine | manage_camera | create, configure presets, extensions |
| Materials/Shaders | manage_material / manage_shader | create, assign, configure |
| Animation | manage_animation | clips, controllers, states |
| UI elements | manage_ui | create, layout, style |
| VFX | manage_vfx | particles, effects |
| Prefabs | manage_prefabs | create, instantiate, modify |
| ScriptableObjects | manage_scriptable_object | create, edit |
| Packages | manage_packages | install, remove, search |
| Builds | manage_build | configure, build, switch platform |
| Tests | run_tests | execute, get results |
| Profiling | manage_profiler | sessions, timing, memory |
| Graphics stats | manage_graphics | rendering stats, pipeline |
| Console output | read_console | errors, warnings, logs |
| API inspection | unity_reflect | live C# reflection |
| Documentation | unity_docs | official Unity docs |
| C# scripts | create_script / validate_script | create, validate |
When creating new scenes, use templates for quick setup:
manage_scene action:"create" template:"3d_basic"
// Creates scene with: Main Camera, Directional Light
manage_scene action:"create" template:"2d_basic"
// Creates scene with: Main Camera (orthographic)
If an MCP operation fails:
read_console — get the error message| Operation | Use MCP | Use File Edit |
|---|---|---|
| Create GameObjects | Yes | Never |
| Edit scenes | Yes | Never |
| Edit prefabs | Yes | Never |
| Write C# scripts | Either | Preferred for complex scripts |
| Configure components | Yes | Never |
| Modify ProjectSettings | Yes | Never |
| Edit .shader/.hlsl files | No (Write tool) | Yes |
| Edit .uxml/.uss files | No (Write tool) | Yes |
| Edit .asmdef files | No (Write tool) | Yes |
If the user has multiple Unity Editor instances:
unity_instances resource → list all running editors
set_active_instance → route commands to specific editor
Always check which instance is active before sending commands.