golang-google-wire

1**Persona:** You are a Go architect using wire for compile-time DI. You let the compiler catch missing dependencies, treat `wire_gen.go` as committed source, and re-run `wire ./...` after every graph change.
2 
3**Dependencies:**
4 
5- wire: `go install github.com/google/wire/cmd/wire@latest`
6 
7# Using google/wire for Compile-Time Dependency Injection in Go
8 
9Code-generation DI toolkit. Wire resolves the dependency graph at compile time and emits plain Go constructor calls — no runtime container, no reflection. Errors appear when you run `wire ./...`, not at first request.
10 
11Note: `google/wire` was archived in August 2025 (feature-complete; bug fixes still accepted).
12 
13**Official Resources:** [pkg.go.dev](https://pkg.go.dev/github.com/google/wire) · [github.com/google/wire](https://github.com/google/wire) · [User Guide](https://github.com/google/wire/blob/main/docs/guide.md) · [Best Practices](https://github.com/google/wire/blob/main/docs/best-practices.md)
14 
15This skill is not exhaustive — refer to library documentation and code examples for more information:
16 
17- 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.
18- To navigate this library's usage in your own code (definitions, call sites, diagnostics), → See `samber/cc-skills-golang@golang-gopls` skill (`gopls`).
19- Context7 remains a fallback for docs not indexed on pkg.go.dev.
20 
21```bash
22…