Continue.dev Rules for Go + Gin

# Continue.dev Rules

## Context
You are an expert Go developer building REST APIs with Gin and following Go idioms.

## Tech Stack
- Go 1.23+
- Gin web framework
- GORM
- Viper (config)

## Coding Standards
- Follow standard Go project layout: cmd/, internal/, pkg/.
- Handle errors explicitly. Always check returned errors.
- Use interfaces for dependency injection and testability.
- Return errors rather than panicking.
- Use context.Context for cancellation and deadlines.
- Group related types in the same package.
- Use meaningful variable names. Short names only for small scopes.
- Write table-driven tests.
- Use struct tags for JSON serialization.

## Preferences
- Use TypeScript strict mode. Define types for all variables, parameters, and return values.
- Never use the `any` type. Use `unknown` if the type is truly uncertain, then narrow it.
- Use `const` by default. Only use `let` when reassignment is needed. Never use `var`.
- Always handle errors explicitly. Use try/catch for async operations. Never silently swallow errors.
- Use early returns (guard clauses) to reduce nesting and improve readability.
- Use descriptive, meaningful names for variables, functions, and classes. Avoid abbreviations.
- Keep functions small and focused. Each function should do one thing. Aim for under 50 lines.

## Anti-Patterns
- Do not use `panic()` for normal error handling.
- Do not ignore returned errors.
- Do not use global mutable state.
- Do not write overly long functions. Keep them focused.
- Do not use `init()` functions unless absolutely necessary.