What problem does it solve? Running multiple implementation workers against the same repository causes port conflicts, shared mutable state, and platform differences between macOS, WSL/Linux, and remote providers. This Skill defines the isolation rules and reproducibility targets so each worker gets an independent, verifiable runtime. ## Core Features & Use Cases - Worker Isolation Invariants: Enforces one isolated workspace and runtime per implementation worker, with no shared mutable state and no host Docker socket or master credentials passed to workers. - Cross-Platform Guidance: Covers Apple Silicon arm64 targeting, WSL2 filesystem and permission pitfalls, and architecture-sensitive dependency verification between local and CI environments. - Worktrunk Integration: Uses Worktrunk as a workspace lifecycle adapter with deterministic port assignment via hash_port templates and bind-conflict detection at startup. - Use Case: When spinning up three parallel implementation workers on a Linux-oriented repo from a Windows machine, apply this Skill to keep each worker's checkout, database, ports, and build output fully isolated inside WSL. ## Quick Start Ask the agent to create an isolated sandbox runtime for a new implementation worker following the sandbox-runtime isolation rules.
