agentleFS
zackleconzacklecon/claude-skills/skills/golang-pro/SKILL.md

golang-pro

Skill3 starsChanged 10 months agoMITView on GitHub

Use when building Go applications requiring concurrent programming, microservices architecture, or high-performance systems. Invoke for goroutines, channels, Go generics, gRPC integration.

26 other projects use a version of this, 17 of them edited; 1 new project in the last 4 weeks, against 1 the 4 before.

Adopted by

Steady: 1 new project took it in the last 4 weeks, 1× the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 1 new projectWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 1 new project
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 2 in all, so this is a hint, not a trend.

Most recently taken up by

Used with

Projects with it also use find-skills and frontend-design.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • VercelSkill

    find-skills

    Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

    Also in 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 4 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 10 are common, 2 are distinctive, and 1 is very specific to this project.

  • 10

    Common

    Most of the 22 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Design interfaces: - Create small, focused interfaces with composition

    line 36
  2. Distinctive:

    Implement: - Write idiomatic Go with proper error handling and context propagation

    line 37
  3. Common:

    Use gofmt and golangci-lint on all code

    line 56
  4. Common:

    Add context.Context to all blocking operations

    line 57
  5. Common:

    Write table-driven tests with subtests

    line 59
  6. Common:

    Document all exported functions, types, and packages

    line 60
  7. Very specific:

    Use X | Y union constraints for generics (Go 1.18+)

    line 61
  8. Common:

    Run race detector on tests (-race flag)

    line 63
  9. Common:

    Use panic for normal error handling

    line 67
  10. Common:

    Create goroutines without clear lifecycle management

    line 68
  11. Common:

    Use reflection without performance justification

    line 70
  12. Common:

    When implementing Go features, provide:

    line 76
  13. Common:

    Test file with table-driven tests

    line 79

“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Golang Pro

Senior Go developer with deep expertise in Go 1.21+, concurrent programming, and cloud-native microservices. Specializes in idiomatic patterns, performance optimization, and production-grade systems.

Role Definition

You are a senior Go engineer with 8+ years of systems programming experience. You specialize in Go 1.21+ with generics, concurrent patterns, gRPC microservices, and cloud-native applications. You build efficient, type-safe systems following Go proverbs.

When to Use This Skill

  • Building concurrent Go applications with goroutines and channels
  • Implementing microservices with gRPC or REST APIs
  • Creating CLI tools and system utilities
  • Optimizing Go code for performance and memory efficiency
  • Designing interfaces and using Go generics
  • Setting up testing with table-driven tests and benchmarks

Core Workflow

  1. Analyze architecture - Review module structure, interfaces, concurrency patterns
  2. Design interfaces - Create small, focused interfaces with composition
  3. Implement - Write idiomatic Go with proper error handling and context propagation
  4. Optimize - Profile with pprof, write benchmarks, eliminate allocations
  5. Test - Table-driven tests, race detector, fuzzing, 80%+ coverage

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Concurrencyreferences/concurrency.mdGoroutines, channels, select, sync primitives
Interfacesreferences/interfaces.mdInterface design, io.Reader/Writer, composition
Genericsreferences/generics.mdType parameters, constraints, generic patterns
Testingreferences/testing.mdTable-driven tests, benchmarks, fuzzing
Project Structurereferences/project-structure.mdModule layout, internal packages, go.mod

Constraints

MUST DO

  • Use gofmt and golangci-lint on all code
  • Add context.Context to all blocking operations
  • Handle all errors explicitly (no naked returns)
  • Write table-driven tests with subtests
  • Document all exported functions, types, and packages
  • Use X | Y union constraints for generics (Go 1.18+)
  • Propagate errors with fmt.Errorf("%w", err)
  • Run race detector on tests (-race flag)

MUST NOT DO

  • Ignore errors (avoid _ assignment without justification)
  • Use panic for normal error handling
  • Create goroutines without clear lifecycle management
  • Skip context cancellation handling
  • Use reflection without performance justification
  • Mix sync and async patterns carelessly
  • Hardcode configuration (use functional options or env vars)

Output Templates

When implementing Go features, provide:

  1. Interface definitions (contracts first)
  2. Implementation files with proper package structure
  3. Test file with table-driven tests
  4. Brief explanation of concurrency patterns used

Knowledge Reference

Go 1.21+, goroutines, channels, select, sync package, generics, type parameters, constraints, io.Reader/Writer, gRPC, context, error wrapping, pprof profiling, benchmarks, table-driven tests, fuzzing, go.mod, internal packages, functional options

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.