Generate production-ready Go Cursor rules for Project Rules (.mdc), AGENTS.md, or legacy .cursorrules. This template encodes stack-specific conventions for projects using Go. Statically typed compiled language with goroutines, channels, and built-in tooling.
The template focuses Cursor AI on concrete Go practices instead of generic coding advice. Required sections are always included; optional sections can be enabled when they match your project.
The generator turns these sections into Project Rules with frontmatter, AGENTS.md, or a single .cursorrules file depending on the output format you choose.
- Follow standard Go project layout (cmd/, internal/, pkg/).
- Use camelCase for unexported identifiers.
- Use PascalCase for exported identifiers.
- One package per directory — avoid package sprawl.
- Keep packages focused and cohesive (single responsibility).
- Use internal/ for code that must not be imported externally.- Always handle errors explicitly — never ignore returned errors.
- Use if err != nil pattern consistently.
- Wrap errors with fmt.Errorf("context: %w", err) to preserve the chain.
- Use errors.Is() and errors.As() for error inspection.
- Define custom error types with Error() method.
- Return errors as the last return value.- Use goroutines for concurrent operations — Go's primary concurrency primitive.
- Use channels for communication between goroutines.
- Use context.Context for cancellation and deadline propagation.
- Use sync.WaitGroup for waiting on goroutine completion.
- Use sync.Mutex or sync.RWMutex for shared state protection.
- Prefer channels over mutexes when communicating between goroutines.