What problem does it solve? Adding a new feature to a Go clean-architecture backend requires touching many wiring points — the DI registry, per-feature setup files, and route registration in main.go — and mistakes in ordering or auth middleware placement can silently expose or lock down routes. This Skill encodes the exact conventions so new features are wired correctly the first time. ## Core Features & Use Cases - Feature wiring guidance: Enforces the pattern of creating internal/bootstrap/{feature}/setup.go with a Setup(r, reg) function and registering it in SetupCleanArchComponents. - Registry conventions: Mandates lazy nil-check-then-construct Get{X}Repository() accessors and forbids memoizing external gateways like Stripe or Firebase on the registry. - Auth-aware route registration: Explains the three bootstrap entrypoints (SetupInternalJobs with x-api-key, SetupPublicComponents unauthenticated, SetupCleanArchComponents behind Firebase auth) and how registration order in setupGin determines authentication. - Use Case: When adding a new invoicing feature, follow the six-step checklist to create the repository, usecase, API handler, registry accessor, bootstrap setup file, and the Setup call — then verify with go build and make linter. ## Quick Start Ask the AI to wire a new clean-architecture feature into the Go app, including its registry accessor, bootstrap setup file, and route registration with the correct auth level.
