메뉴
Lazy-load for LUX Unity bridge and MCP game-development operations: status, compile, tests, logs, launch, screenshots, hierarchy, dynamic code, record/replay, and one-loop MCP workflows.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | lux-unity |
| description | Lazy-load for LUX Unity bridge and MCP game-development operations: status, compile, tests, logs, launch, screenshots, hierarchy, dynamic code, record/replay, and one-loop MCP workflows. |
| category | workflow |
| source | lux |
Use this skill only when a request directly involves operating or inspecting a Unity project through LUX.
.lux/ as the project runtime source of truth for specs, execution tickets, run state, and evidence..ledger-style files only as local worktree decision records..lux/ state; do not use remote/WebRTC surfaces as a verification authority.Use lux mcp --project-path <unity-project> when an AI client needs the stdio MCP surface. The game-development tools are:
lux_bridge_install and lux_bridge_diagnostics for bridge setup and health.lux_game_spec_write for .lux/specs/spec.json, GDD/domain specs, and local worktree decision-record creation/import.lux_game_ticket_prepare for one safe .lux/tickets/ first-loop ticket.lux_unity_maneuver for one safe Unity code/scene/settings/package/asset action with evidence.lux_game_dev_loop_once for the full installed-bridge loop, stopping after one verified loop or a specific structured failure.Expected MCP reports include structuredContent, step/evidence references, engine capability status, and a clear stopReason. If Unity or bridge discovery is unavailable, report that blocker directly; do not substitute mock success unless the caller explicitly requested a test harness. Godot and Three.js observations are not equal to Unity maturity unless their adapter-supported evidence is present.
references/backend-status.md for gateway and bridge status.references/compile-tests.md for compile and test flows.references/dynamic-code.md for guarded C# execution.references/launch.md for Unity launch behavior.references/logs.md for logs and event inspection.references/object-hierarchy.md for hierarchy/object inspection.references/playmode-input.md for play mode and input automation.references/record-replay.md for recording and replay.references/screenshots.md for screenshots and visual checks.Report the command or API used, observed result, verification evidence, and any remaining blocker.
Lazy-load only when this workflow is explicitly needed. Use for durable technical choices. Output a short ADR: Context, Decision, Alternatives, Consequences, Verification, Owner. Prefer existing LUX boundaries: gateway owns CLI/server, bridge owns Unity protocol, Skills owns passive workflows. Reject duplicate state, hidden fallback, and broad rewrites without evidence.
Lazy-load only when this workflow is explicitly needed. Use to review an existing design or implementation for boundary drift. Check SSoT, responsibility split, protocol consistency, atomicity, idempotency, and observable failures. Return ranked findings with file references, risk level, and the smallest corrective action.
Lazy-load only when this workflow is explicitly needed. Use when a change risks architectural drift. Enforce: .lux is SSoT; clear subsystem ownership; consistent schemas; atomic operations; idempotent retries; no silent fallback. Report violations and concrete repair steps.
Lazy-load only when this workflow is explicitly needed. Use for high-risk product, automation, or ethical decisions. Run: clarify intent; quantify evidence; check user/data/IP/fairness risks; define stop and rollback conditions; record approval. Verdicts: PASS, REVIEW, or REJECT.
Lazy-load only when this workflow is explicitly needed. Use to turn observed failures into actionable reports. Capture summary, environment, exact steps, expected result, actual result, logs, suspected subsystem, severity, reproducibility, and minimal next diagnostic. Do not invent fallback data.
Lazy-load only when this workflow is explicitly needed. Use to classify and route defects. Determine impact, scope, likely owner, regression window, blocking status, and verification path. Prefer quick reproduction and narrow hypotheses before implementation.