agent-manager / rules
Cursor rule0 starsChanged 8 days agoApache-2.0View on GitHub
Go language-specific development guidelines and patterns
- Installs packages
2 other projects use a version of this.
Adopted by
Most recently taken up by
- giantswarm/mcp-kubernetesword for word, first seen Nov 6, 2026
- giantswarm/musterword for word, first seen Jan 30, 2026
Other versions2 projects use a version of this.
Word for word · 2
- giantswarm/muster★ 40100% same
- giantswarm/mcp-kubernetes★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,157 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/zz_generated.base-llm-rules.mdcCursor rule
The file
We split this zz_generated.go-llm-rules.mdc into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 10
All Go code is expected to adhere to the rules outlined in the Giant Swarm style guide located at …
- Distinctive: line 11
Always fetch and fully understand the style guide before reviewing any code.
- Distinctive: line 13
When applying the style guide, always list all instances of a particular issue, grouped by the finding type.
- Distinctive: line 27
When creating or modifying Go files, perform the according check and mitigate any issues before committing.
- Distinctive: line 31
DO NOT EDIT. Generated with devctl.
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule 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
---
description: Go language-specific development guidelines and patterns
globs: **/*.go,go.mod,go.sum
---
These guidelines apply to Go code and supplement any other general development instructions or workflows.
# Go Code Guidelines
- All Go code is expected to adhere to the rules outlined in the Giant Swarm style guide located at @https://github.com/giantswarm/fmt/tree/main/go .
- Always fetch and fully understand the style guide before reviewing any code.
- The Giant Swarm style guide linked above must always be considered definitive. ALL rules and provisions contained in the style guide MUST be met.
- When applying the style guide, always list all instances of a particular issue, grouped by the finding type.
## Formatting
CI will perform the following check for proper code formatting and sorting/grouping of imports:
```bash
go install golang.org/x/tools/cmd/goimports@latest && \
if [[ -n $(goimports -local github.com/${CIRCLE_PROJECT_USERNAME}/${CIRCLE_PROJECT_REPONAME} -l .) ]];
then
goimports -local github.com/${CIRCLE_PROJECT_USERNAME}/${CIRCLE_PROJECT_REPONAME} -d . && exit 1;
fi
```
When creating or modifying Go files, perform the according check and mitigate any issues before committing.
<!--
DO NOT EDIT. Generated with devctl.
This file is maintained at:
https://github.com/giantswarm/devctl/blob/83dbeb7aedca2abc8fd38c99e3cfa49f58d8ff82/pkg/gen/input/llm/internal/file/go_rules.mdc.template
Manual changes will be overwritten.
-->
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.