Menu
Perform the safest normal hardware validation path through forge run.
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
Carry shared or u64-specific 1541ultimate changes into Spiffy c64u while preserving Spiffy-only behavior such as WASD differences.
Check patch compatibility and export upstreamable 1541ultimate work.
Refresh pinned upstream repos and check patch compatibility.
Build disposable artifacts through the root forge interface.
Inspect or exercise the CI baseline and ordered transient canary workflows.
Handle persistent install, flash, and recovery flows through forge.
| name | transient-device-run |
| description | Perform the safest normal hardware validation path through forge run. |
Use this skill for transient hardware validation and as the default interpretation of ambiguous deploy requests.
u64, c64u.ue2, or no explicit target.--dry-run or --build-tools-dir../forge status so device reachability is visible.u64, run ./forge run u64.c64u or c64u.ue2, run ./forge run c64u.ue2../forge run u64 when u64 is reachable or available../forge run c64u.ue2 only when u64 is not available and c64u is reachable or available.c64u.ue2 uses a FAST_LAUNCH helper by default for unattended Telnet launch.--launcher-confirmation only when the user explicitly wants the stock confirmed launcher for manual testing.c64u.ue2.run over install or flash when the user asks for the safest validation path.install or hard flash just because the transient target preference failed.