菜单
Lazy-load only when this workflow is explicitly needed. Use when adding or refactoring helper utilities for tests. Keep helpers small, deterministic, local to the test domain, and named by behavior. Avoid hiding assertions or creating broad fixtures that mask failures.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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.
| name | test-helpers |
| description | Lazy-load only when this workflow is explicitly needed. Use when adding or refactoring helper utilities for tests. Keep helpers small, deterministic, local to the test domain, and named by behavior. Avoid hiding assertions or creating broad fixtures that mask failures. |
| category | quality |
| source | lux |
Use when adding or refactoring helper utilities for tests. Keep helpers small, deterministic, local to the test domain, and named by behavior. Avoid hiding assertions or creating broad fixtures that mask failures.
Do not preload this skill during startup, hot reload, or background indexing. Read it only when the user request directly matches this workflow.
