菜单
Use when tracing runtime behavior in C64 Commander from UI events through state updates, async queues, throttling, and device requests.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when capturing a new device-menu YAML (a new family or firmware) and bootstrapping its REST<->menu association for the Config-page menu mapping layer, or when re-validating/extending the existing C64U mapping. Covers the draft_association.py authoring aid and the compile-menu-mapping pipeline.
Use when hardware validation or debugging needs the adb-attached Pixel 4 plus a reachable Ultimate device over REST in C64 Commander. Prefer u64 when both u64 and c64u are reachable.
Use when auditing README, docs/**, docs/, or in-app documentation for stale guidance, contradictions, undocumented behavior, or screenshot drift in C64 Commander.
Use when building a repository inventory for C64 Commander, including subsystem boundaries, runtime entry points, and major module responsibilities.
Raise Codecov-reported test coverage for C64 Commander to a defined target without duplicating tests or degrading signal quality.
Production hardening workflow for C64 Commander covering CI integrity, Docker images, Node runtime, artifact consistency, and release stability.
| name | runtime-traversing |
| description | Use when tracing runtime behavior in C64 Commander from UI events through state updates, async queues, throttling, and device requests. |
| argument-hint | (optional) feature or flow to trace |
| user-invocable | true |
| disable-model-invocation | true |
Explain how a user action propagates through runtime layers and where fragile timing or queue behavior may exist.
Trace the path:
UI event → state change → async queue → device request.
Identify:
