occam-golisted
Install: claude install-skill stephenoffer/occam
# Go
Read the actual manifest and conventions before choosing commands, and use the ecosystem's established tools. Don't translate patterns from another language mechanically.
- **Tooling:** check `go.mod`, build tags, `go vet` and the project's linter. Run `go test -race` for concurrent code.
- **Errors:** handle every returned error and wrap with `%w`. Don't panic across package boundaries for expected failures.
- **Concurrency:** every goroutine needs a way to stop. Pass `context.Context` and respect its cancellation, and don't ignore deadlines on network calls. Unbounded goroutine creation is a leak waiting for load, and closing channels is the sender's job.
- **Nil and values:** a nil pointer in an interface isn't a nil interface. Writing to a nil map panics. Range variables and slice aliasing depend on the Go version and capacity.
- **Resources:** `defer` runs at function end, not loop end, so closing in a loop needs a helper. Always close response bodies.
- **Interfaces:** accept small interfaces and return concrete types. A new interface with one implementation needs a reason.
- **Structure:** a package is the unit of design, named for what it provides rather than `util` or `common`. `internal/` stops other modules importing it. Import cycles don't compile, so move the shared piece down.
- **Naming:** `MixedCaps`, short lowercase package names, and no stutter: `http.Server`, not `http.HTTPServer`. Getters drop `Get`, and acronyms keep their case, as in `ID` and `URL