skillshare-devcontainer

Execute CLI commands and tests inside the devcontainer. The host machine is macOS but the project binary is Linux — running CLI commands on the host will silently produce wrong results or fail. This skill prevents that mistake. ## When to Use This - Running `ss` / `skillshare` commands for verification - Running `go test`, `make test`, `make check` - Reproducing a bug report - Testing a feature you just implemented - Starting the web UI dashboard - Any command that needs the skillshare binary or Go toolchain ## When NOT to Use This - Editing source code (do that on host via Read/Edit tools) - Running `git` commands (git works on host) - Running `make fmt`, `make lint` (host-safe Go toolchain commands; no container needed) - E2E test runbooks → use `cli-e2e-test` skill instead (it handles ssenv isolation) ## Architecture: Two Layers of Isolation ``` Host (macOS) └─ Devcontainer (Linux, Debian-based) ├─ Default HOME: /home/developer (persistent volume) ├─ Source: /workspace (bind-mount of repo root) └─ ssenv environments: ~/.ss-envs/<name>/ (isolated HOME dirs) ``` **Devcontainer** = Linux environment with Go, git, pnpm, air (hot-reload). Source code is at `/workspace` (bind-mount of the host repo). The `ss` / `skillshare` wrapper auto-builds from source on every invocation — **no manual `make build` needed**. Edit code on the host, then immediately `docker exec` to run it; the change is picked up automatically. **ssenv** = Isolated HOME directori...