Rules for Go backend services enforcing idiomatic Go patterns, proper error handling, and clean architecture conventions.
Enforces idiomatic Go: explicit error handling (no panic in library code), table-driven tests, context propagation, structured logging with slog, interface-based dependencies, proper goroutine lifecycle management, and standard project layout. Covers chi/gin router patterns and SQLC for database queries.
Workflows from the Neura Market marketplace related to this Cursor resource