القائمة
Use when auditing README, docs/**, docs/, or in-app documentation for stale guidance, contradictions, undocumented behavior, or screenshot drift in C64 Commander.
التثبيت باستخدام 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 building a repository inventory for C64 Commander, including subsystem boundaries, runtime entry points, and major module responsibilities.
Use when tracing runtime behavior in C64 Commander from UI events through state updates, async queues, throttling, and device requests.
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 | doc-audit |
| description | Use when auditing README, docs/**, docs/, or in-app documentation for stale guidance, contradictions, undocumented behavior, or screenshot drift in C64 Commander. |
| argument-hint | (optional) scope such as README, diagnostics, platform docs, or screenshots |
| user-invocable | true |
| disable-model-invocation | true |
Compare implementation against documentation and identify drift that affects contributors or end users.
Compare implementation against documentation.
Check:
Identify:
Report:
