tech-go
Skill1 starsChanged 28 days agoMITView on GitHub
Technology skill loaded when writing Go backend services or CLIs.
In this repository29 other files it gives its agents.
- exec-accessibilitySkill
- exec-architectureSkill
- exec-code-reviewSkill
- exec-debuggingSkill
- exec-documentationSkill
- exec-performanceSkill
- exec-refactoringSkill
- exec-repo-patternsSkill
- exec-securitySkill
- exec-testingSkill
- exec-ui-uxSkill
- exec-verificationSkill
- tech-dockerSkill
- tech-flutterSkill
- tech-graphqlSkill
- tech-kotlinSkill
- tech-nextjsSkill
- tech-nodeSkill
- tech-postgresSkill
- tech-pythonSkill
- tech-reactSkill
- tech-rustSkill
- tech-swiftSkill
- tech-tailwindSkill
- tech-typescriptSkill
- tech-vueSkill
- linear-spanks-gitSkill
- linear-spanksSkill
- linear-workflowSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
When writing Go, prioritize simplicity, explicit error handling, and idiomatic standard library usage:
- Very specific: line 13
Error Handling: Do not ignore errors. Always check if err != nil.
- Very specific: line 14
Context: Always pass context.Context as the first argument to functions that do I/O (network, database) to enable timeouts and cancellation.
- Distinctive: line 15
Concurrency: Use goroutines for concurrent tasks, but always know how they will terminate.
- Distinctive: line 17
Standard Library: Prefer the standard library over third-party packages for routing, HTTP clients, and string manipulation unless the …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Go Best Practices
Apply this skill after inspecting repository conventions and supported versions. Treat its rules as defaults unless they protect a concrete safety property; preserve an established project pattern when it conflicts, and record the reason in the implementation plan.
When writing Go, prioritize simplicity, explicit error handling, and idiomatic standard library usage:
- Error Handling: Do not ignore errors. Always check
if err != nil. Avoidpanicin production code; return errors up the stack. - Context: Always pass
context.Contextas the first argument to functions that do I/O (network, database) to enable timeouts and cancellation. - Concurrency: Use goroutines for concurrent tasks, but always know how they will terminate. Prevent goroutine leaks by using WaitGroups or channels.
- Interfaces: Define interfaces where they are used (consumer side), not where they are implemented (producer side). Keep interfaces small (1-2 methods).
- Standard Library: Prefer the standard library over third-party packages for routing, HTTP clients, and string manipulation unless the standard library is proven insufficient.
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
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.