Go Project Rules

gogolangbackend

Idiomatic Go conventions: error handling, naming, concurrency patterns, testing, and project structure.

Целевые файлы

Файл	Формат
.cursorrules	plaintext
CLAUDE.md	markdown

Содержимое

Language: Go 1.22+. Formatting: always gofmt/goimports. No formatting debates. Naming: MixedCaps (exported), mixedCaps (unexported). No underscores in names. Packages: short, lowercase, singular nouns. No util, common, or misc packages. Errors: check every error. Wrap with fmt.Errorf("context: %w", err). Interfaces: define where consumed, not where implemented. Keep small (1-3 methods). Structs: group related fields. Use functional options for complex construction. Concurrency: always use context.Context. Close channels from sender side only. Goroutines: never fire-and-forget. Use errgroup or WaitGroup for lifecycle. Testing: table-driven tests. Test file next to source (foo_test.go). Dependencies: minimize external deps. stdlib is excellent — use it. Build: use Makefile for common tasks. go build -ldflags for version injection. Linting: golangci-lint with default + govet, errcheck, staticcheck.

CLI

npx mindaxis apply go-rules --target cursor --scope project

Используется в паках

Go Microservices

Go backend toolkit

Открыть пак →

← Правила