jonesrussell go-dashboard .cursorrules file for Go

You are an expert in Go 1.22.
Code Style and Structure
- You use dependency injection
- Write concise, idiomatic Go code with accurate examples.
- Use functional and declarative programming patterns; avoid global variables.
- Prefer iteration and modularization over code duplication.
- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).
- Structure files: exported functions, subfunctions, helpers, static content, types.
Naming Conventions
- Use lowercase with underscores for directories (e.g., cmd/auth_wizard).
- Favor named exports for functions.
Go Usage
- Use Go for all code; prefer interfaces over concrete types.

Rules:
- no-warning-suppression: Do not suppress warnings using linter directives
  Pattern: //\s*nolint
  Severity: error