Cursor rule

1---
2description: 
3globs: *.go
4alwaysApply: false
5---
6# Go Development Rules for Cursor
7 
8## Project Structure
9- Use `cmd/${program}/main.go` for main applications
10- Use `pkg/**/*.go` for shared libraries and packages
11- Keep packages focused and cohesive
12 
13## Build and Run Commands
14- NO Make - use simple Go commands only
15- Build: `go build ./cmd/har-mcp`
16- Run: `go run ./cmd/har-mcp`
17- Test: `go test ./...`
18- Format: `go fmt ./...`
19- Vet: `go vet ./...`
20- Tidy dependencies: `go mod tidy`
21 
22## Code Style
23- Follow standard Go formatting with `gofmt`
24- Use standard Go naming conventions (PascalCase for exported, camelCase for unexported)
25- Keep functions and methods small and focused
26- Use meaningful variable and function names
27- Avoid unnecessary else clauses when using early returns
28 
29## Coding
30- You should have access to a godoc tool. Use it as much as possible
31- Don't guess interfaces. Use the tools that you have to doublecheck what you are doing is correct
32 
33## Testing
34- Use github.com/stretchr/testify for assertions
35- NO table-driven tests - use test helpers instead
36- Test file naming: `*_test.go`
37- Test function naming: `TestFunctionName`
38- Use `require` for test setup that must succeed, `assert` for actual test assertions
39- Create helper functions to reduce test duplication
40- Test one thing per test function
41 
42## Error Handling
43- Always handle errors explicitly
44- Use meaningful error messages
45- Wrap errors with context using `fmt.Errorf("context: %w", err)`
46- Return errors as the last return value
47 
48## Dependencies
49- Minimize external dependencies
50- Use standard library when possible
51- Pin dependency versions in go.mod
52 
53## Comments
54- Use godoc style comments for exported functions and types
55- Comment explains WHY, not WHAT
56- Keep comments concise and up-to-date
57 
58## Performance
59- Avoid premature optimization
60- Profile before optimizing
61- Use appropriate data structures
62- Be mindful of memory allocations in hot paths
63 
64## Concurrency
65- Use channels for communication between goroutines
66- Avoid shared mutable state
67- Use context.Context for cancellation and timeouts
68- Prefer composition over inheritance