Menu
Use when tracing runtime behavior in C64 Commander from UI events through state updates, async queues, throttling, and device requests.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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:
