skillshare-devcontainer

1Execute 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.
2 
3Before acting, run `python3 scripts/ai-context.py testing` and follow that topic. The topic is the source of truth for repository execution boundaries and test rules; this skill retains the interactive workflow and command recipes.
4 
5## When to Use This
6 
7- Running `ss` / `skillshare` commands for verification
8- Running `go test`, `make test`, `make check`
9- Reproducing a bug report
10- Testing a feature you just implemented
11- Starting the web UI dashboard
12- Any command that needs the skillshare binary or Go toolchain
13 
14## When NOT to Use This
15 
16- Editing source code (do that on host via Read/Edit tools)
17- Running `git` commands (git works on host)
18- Running `make fmt`, `make lint` (host-safe Go toolchain commands; no container needed)
19- E2E test runbooks → use `cli-e2e-test` skill instead (it handles ssenv isolation)
20 
21## Architecture: Two Layers of Isolation
22 
23```
24Host (macOS)
25  └─ Devcontainer (Linux, Debian-based)
26       ├─ Default HOME: /home/developer (persistent volume)
27       ├─ Source: /workspace (bind-mount of repo root)
28       └─ ssenv environments: ~/.ss-envs/<name>/ (isolated HOME dirs)
29```
30…