Own host, workstation, container, and team bootstrap surfaces. Use when defining local prerequisites, dev containers, bootstrap scripts, and local infrastructure bring-up without taking over runtime config ownership.
system-environment-setup is the canonical infrastructure owner for host/system/team bootstrap.
It owns developer machine prerequisites, containerized local environments, bootstrap scripts, and local tooling conventions. It does not own the runtime config schema itself and must defer runtime variable meaning to ../environment-setup/SKILL.md.
Capture:
If bootstrap instructions require env vars, reference the runtime config owner instead of redefining the variables here.
This skill can say how contributors obtain or inject config locally, but not what the runtime config contract means.
Prefer:
Local Docker Compose, dev containers, Make targets, and helper scripts live here when they are about contributor bootstrap.
Deployment pipelines, promotion rules, and rollback policy do not.
Check whether a new contributor can answer:
## Local Bootstrap
### Prerequisites
- tool name + minimum version
### Startup path
1.
2.
3.
### Local services
- service
- how to start it
### Config handoff
- points to runtime config owner:
system-environment-setup owns workstation/local bootstrap.environment-setup still owns runtime config shape and validation.deployment-automation owns deploy/release behavior..env semantics instead of linking to the runtime config ownerenvironment-setup