devsandbox-configlisted
Install: claude install-skill zekker6/devsandbox
# devsandbox configuration
Answer configuration questions from the devsandbox documentation, fetched at the time you answer.
## The one rule
**Every section, key and value you name must come from a source you read in this session.**
devsandbox ignores a key it does not recognize rather than rejecting it, so an invented key produces a config that looks applied and does nothing. A guess here is worse than no answer. If you cannot find a setting, say it does not exist and name where you looked. Never derive a key from a similar one - `keep_container` has no `keep_containers`, and `[tools.git]` taking `mode` does not mean `[tools.docker]` does.
**If the documentation cannot be fetched, say so and stop.** No network means no grounding, and answering from memory is the failure this skill exists to prevent. Offer the local alternatives below instead.
## Sources, most authoritative first
1. **A devsandbox checkout, if one is at hand.** When the working directory is the devsandbox repository, read `docs/*.md` directly - those match the code in front of you, and `grep -n 'toml:"' internal/config/config.go` lists every key of the fixed schema. Prefer this over fetching.
2. **The user's own machine**, for anything that depends on their setup rather than on what the software supports:
```bash
devsandbox config path # where the global config lives
devsandbox config show # the resolved configuration, after merging
devsandbox doctor # installatio