// Apply onepixel repository conventions for env loading, DB backend selection, auth locals, error payloads, and shortcode semantics.
| name | conventions |
| description | Apply onepixel repository conventions for env loading, DB backend selection, auth locals, error payloads, and shortcode semantics. |
Use this skill when touching config, middleware, request/response handling, or URL creation/lookup logic.
From src/config/env.go:
ENV=test loads onepixel.test.env and changes CWD to repo root.ENV=production or RAILWAY_ENVIRONMENT=production) loads onepixel.production.env.onepixel.local.env is loaded as fallback defaults.From src/config/vars.go and src/db/init.go:
USE_FILE_DB=true -> sqlite + duckdb providers.COMMON_APP_EVENT_DB=true makes events DB reuse app DB URL.db.InjectDBProvider in tests/providers/test_db_providers.go.Use locals keys from src/config/consts.go:
LOCALS_USER ("user")LOCALS_ADMIN ("admin")dtos.CreateErrorResponse, parser/validator send helpers) instead of ad hoc JSON error payloads.src/utils/radix64.go).src/controllers/urls.go assumes radix64 encoding.make build DOCS=false.make docs only when route annotations or API docs-facing metadata changed.Reference for all onepixel API endpoints, their HTTP methods, paths, auth requirements, and behavior.
Understand onepixel database topology by environment, data ownership across app/events stores, and initialization/migration behavior.
Understand onepixel runtime architecture, host-based app dispatch, and redirect analytics flow before changing behavior across routes/controllers/db.
Build and run onepixel binaries, generate Swagger docs when needed, and produce cross-platform release artifacts.
Run onepixel unit and e2e tests with correct env setup, coverage artifacts, and troubleshooting guidance for GeoIP/network-related failures.