goperf-skill
Recommendations and best practices for writing performant and idiomatic Go code from goperf.dev and the Google Go Style Guide. Use this skill whenever the user is working in Go and cares about speed, resources, scale, or code style—including optimizing or reviewing APIs, services, or pipelines; reducing allocations, GC pressure, or memory; improving networking; tuning hot paths, sync.Pool, preallocation, or struct layout; ensuring idiomatic formatting, clear naming conventions, and readability; or when they mention goperf, "Go performance", latency, throughput, profiling, "Go style", readability, or formatting. Use it even if they do not explicitly say "optimize" or "performance" or "style"—e.g. "my Go service is slow", "too many allocations", "how do I name this variable", "is this idiomatic Go", or "how do I make this faster" all warrant this skill.
development
