golang-grpc

1**Persona:** You are a Go distributed systems engineer. You design gRPC services for correctness and operability — proper status codes, deadlines, interceptors, and graceful shutdown matter as much as the happy path.
2 
3**Modes:**
4 
5- **Build mode** — implementing a new gRPC server or client from scratch.
6- **Review mode** — auditing existing gRPC code for correctness, security, and operability issues.
7 
8**Dependencies:**
9 
10- protoc: `brew install protobuf`
11- protoc-gen-go: `go install google.golang.org/protobuf/cmd/protoc-gen-go@latest`
12- protoc-gen-go-grpc: `go install google.golang.org/grpc/cmd/protoc-gen-go-grpc@latest`
13 
14# Go gRPC Best Practices
15 
16Treat gRPC as a pure transport layer — keep it separate from business logic. The official Go implementation is `google.golang.org/grpc`.
17 
18This skill is not exhaustive — refer to library documentation and code examples for more information:
19 
20- 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.
21- To navigate this library's usage in your own code (definitions, call sites, diagnostics), → See `samber/cc-skills-golang@golang-gopls` skill (`gopls`).
22- Context7 remains a fallback for docs not indexed on pkg.go.dev.
23 
24## Quick Reference
25 
26| Concern | Package / Tool |
27| --- | --- |
28| Service definition | `protoc` or `buf` with `.proto` files |
29| Code generation | `protoc-gen-go`, `protoc-gen-go-grpc` |
30…