What problem does it solve? Developing Entangled Desktop on this two-host machine (Windows native plus WSL Ubuntu) fails in predictable, expensive ways: cargo target dirs fill the 50 GB D: drive, the WSL VHDX grows until C: hits zero and kills every running VM, stale artifacts cause false test failures, and WSL's fast clock corrupts timing measurements. This Skill encodes the hard-won rules that prevent those outages before any build, worktree, or VM launch. ## Core Features & Use Cases - Dual-host build discipline: Canonical cargo commands for WSL and Windows with per-branch CARGO_TARGET_DIR locations, plus the rustup update requirement so local clippy matches CI. - Disk-space safety rules: Per-task target dir cleanup with scripts/dev-clean.sh --mine, a strict prohibition on machine-wide cleanup (wsl --shutdown, docker prune, VHDX compaction), and a 10 GB free-space stop sign on C:. - VM and artifact gotchas: Rules for demo VM disks (sparse copies, never share a writable image), stale initramfs/firmware rebuild triggers, fetched bootstrap kernels, and the WSL clock skew that skews every benchmark. - Use Case: Before an agent starts a worktree to fix a virtio-net bug, it loads this Skill to set the correct target dir on both hosts, verify disk space, fetch the pinned firmware, and avoid deleting shared VM images belonging to other tasks. ## Quick Start Load the dev-environment skill before building or testing anything in the Entangled Desktop repository so the correct target dirs, disk rules, and host commands are applied.
