go-hints

Project-wide Go guidance. Apply these rules when authoring or modifying Go code in this repository.

When to apply

Apply when any of the following is true:

• The task touches a file matching **/*.go, **/go.mod, or **/go.sum
• The user is designing a Go package, service, or CLI
• The user asks about Go idioms, error handling, concurrency, HTTP handlers, dependency injection, or performance tuning
• The user is writing or reviewing Go tests, test helpers, table-driven tests, golden files, or integration tests

How to apply

1. Before writing or editing Go code, load the reference file(s) relevant to the task. Do not rely on memory — these rules may evolve.
2. Prefer the obvious, readable solution. Do not introduce abstractions, closures, or indirection that the task does not require.
3. Match the repository's existing patterns before applying a rule from the references — if a file already follows a rule, stay consistent; if it violates one, surface the mismatch rather than silently "fixing" surrounding code.
4. For test changes, confirm which kind of test (unit vs. integration) and which isolation strategy the project uses before adding new tests.