environmentslisted

# environments The environment-strategy umbrella for robium. Every robium build needs an answer to "how does this run, identically, on my laptop and on whatever server it ends up on" before the first line of application code is written. This skill decides uv vs venv vs Docker, and — once Docker is chosen — how to get GPU passthrough and remote/headless display right. It does not own multi-module application Dockerfiles or compose wiring across nodes; that's `integration`. ## When to use this skill - Starting any new robotics project and the environment strategy isn't decided yet — this is a required early step, not an optional one. - The trigger phrases in the description: 'uv', 'venv', 'virtualenv', 'docker for this project', 'reproducible environment', 'GPU in container'. - Debugging "works on my machine but not on the server" — almost always an environment-parity bug, not an application bug. - Cross-references — go to the sibling skill instead when the question is: - Wiring multiple app modules together, Dockerfiles for a multi-node app, or compose files spanning services → `integration` (this skill covers a *single* environment's shape; `integration` covers the app that runs in it). - Remote visualization once headless is decided → `foxglove`. - ROS 2-specific package/build questions once Docker + ROS 2 is chosen → `ros2`. - Picking a manipulation/training framework once the env is settled → `lerobot`. - The whole-stack decision this fee