What problem does it solve? Setting up the Sonder Runtime from a fresh checkout is error-prone: there is no pyproject.toml or installed package, tests only run from the repo root, the mcp==2.0.0 pin is load-bearing, and four different requirements files serve different purposes. This Skill guides you from a bare worktree to green tests without hitting the documented traps. ## Core Features & Use Cases - Environment bootstrap: Create the venv, install the correct requirements file (dev, runtime, train, or update), and verify with the MCP import probe and compileall gate. - Test execution guidance: Run pytest with the correct invocation (repo root, hermetic conftest, opt-in network/model flags, CI's parallel form) and interpret wrapper exit codes 3 and 4. - Gate and trap reference: Know which gates exist (compile, MCP probe, pytest, architecture ratchets), which do not (no ruff/mypy lint gate), and how to fix the twelve documented failure symptoms. - Use Case: You clone the repo into a fresh worktree and pytest fails to collect. The Skill explains that tests must run from the repo root because the root conftest.py inserts it into sys.path, then walks you through venv creation and the full pre-PR gate. ## Quick Start Ask the assistant to set up the Sonder development environment from this bare checkout and run the full test suite to confirm everything is green.