myvocap-backend
Persona: You are the MyVocab backend engineer. You know every pattern in this codebase intimately. When writing new code, you reproduce the exact file layout, naming, error flow, and DI wiring that existing features use — no improvisation, no "better" alternatives. When reviewing code, you check against the repo's pre-commit checklist.
Precedence: This skill overrides generic jimmy-skills@backend-go-* skills when they conflict. The codebase conventions documented here are the source of truth.
Modes:
- Build mode — adding a new feature or endpoint: scaffold from the feature module template, wire in
cmd/app/http.go, run quality gates. - Review mode — auditing code changes: run the pre-commit checklist, flag violations.
Quick Reference
| Concept | Pattern | Reference |
|---|---|---|
| Feature layout | internal/feature/<name>/{types,repository,service,handler,routes,provider,errors}.go |
references/feature-module-template.md |
| DI wiring | Deps struct + Provide(d Deps) *Handler |
references/feature-module-template.md |
| Error flow | sentinel → toAppError() → writeError() → httpresponse.WriteError() |
references/error-flow.md |
| Repository | sqlc-only (sqlcgen.Queries), domain type conversion via *FromRow() |
references/feature-module-template.md |
| Caching | cache.FetchOne / cache.FetchWithSingleflight + graceful nil degradation |
references/cache-event-patterns.md |
| Events | event.Bus / event.Publisher + Noop() fallback + registerListeners() |
references/cache-event-patterns.md |
More from jimnguyendev/jimmy-skills
backend-go-testing
Provides a comprehensive guide for writing production-ready Golang tests. Covers table-driven tests, test suites with testify, mocks, unit tests, integration tests, benchmarks, code coverage, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, memory leaks, CI with GitHub Actions, and idiomatic naming conventions. Use this whenever writing tests, asking about testing patterns or setting up CI for Go projects. Essential for ANY test-related conversation in Go.
14backend-go-code-style
Golang code style and readability conventions that require human judgment. Use when reviewing clarity, naming noise, file organization, package boundaries, comments, or maintainability tradeoffs in Go code. Do not use this for golangci-lint setup or lint output interpretation; use `jimmy-skills@backend-go-linter` for tooling.
12backend-go-safety
Defensive Golang coding to prevent panics, silent data corruption, and subtle runtime bugs. Use whenever writing or reviewing Go code that involves nil-prone types (pointers, interfaces, maps, slices, channels), numeric conversions, resource lifecycle (defer in loops), or defensive copying. Also triggers on questions about nil panics, append aliasing, map concurrent access, float comparison, or zero-value design.
11engineering-rest-api-design
REST API design conventions covering URL structure, HTTP methods, pagination, async patterns, idempotency, error envelopes, and API documentation standards. Use when designing new endpoints, reviewing API contracts, or establishing API guidelines before implementation in any language.
11backend-go-design-patterns
Idiomatic Golang design patterns for real backend code: constructors, error flow, dependency injection, resource lifecycle, resilience, data handling, and package boundaries. Apply when designing Go APIs, structuring packages, choosing between patterns, making architecture decisions, or hardening production behavior. Default to simple, feature-first designs unless complexity has clearly appeared.
11backend-go-grpc
Provides gRPC usage guidelines, protobuf organization, and production-ready patterns for Golang microservices. Use when implementing, reviewing, or debugging gRPC servers/clients, writing proto files, setting up interceptors, handling gRPC errors with status codes, configuring TLS/mTLS, testing with bufconn, or working with streaming RPCs.
11