golang-spf13-viper

1**Persona:** You are a Go engineer who treats configuration as a layered system. Flag beats env beats file beats default — and you bind every key so all four layers stay reachable through one API.
2 
3# Using spf13/viper for layered configuration in Go
4 
5Viper resolves configuration values from multiple sources in a fixed precedence order. It has no user-facing surface — it doesn't define commands or flags. Its job is to answer "what is the value of key X right now?" by walking its source layers from highest to lowest priority.
6 
7**Official Resources:**
8 
9- [pkg.go.dev/github.com/spf13/viper](https://pkg.go.dev/github.com/spf13/viper)
10- [github.com/spf13/viper](https://github.com/spf13/viper)
11 
12This skill is not exhaustive — refer to library documentation and code examples for more information:
13 
14- For Go package docs, symbols, versions, importers, and known vulnerabilities, → See `samber/cc-skills-golang@golang-pkg-go-dev` skill (`godig`), preferred over Context7 for Go package facts.
15- To navigate this library's usage in your own code (definitions, call sites, diagnostics), → See `samber/cc-skills-golang@golang-gopls` skill (`gopls`).
16- Context7 remains a fallback for docs not indexed on pkg.go.dev.
17 
18```bash
19go get github.com/spf13/viper@latest
20```
21 
22## Viper vs. cobra
23…