Create or revise `TASKS.json` using the repo's uid-first task workflow, persistent registry under `lib/`, and existing task-registry tooling. Use when turning design artifacts into runnable task queues or when maintaining active task backlog state in this repo.
Create or refine the canonical repo-level design plan at `lib/design/design-plan.json` using the shared schema in `lib/design/design-plan.schema.json`. Use when producing architecture or design documents that must later drive task planning or architecture review.
Keep SocialPredict backend route behavior and OpenAPI artifacts synchronized during backend/API work. Use when modifying handlers, route wiring, middleware behavior, request or response shapes, or `backend/docs/openapi.yaml`.
Enforce SocialPredict Go service-boundary governance for backend/API work. Use when implementing or reviewing changes in backend handlers, domain services, repositories, auth service, or route wiring to prevent layer violations, direct DB leakage, and cross-domain coupling.
Apply Go quality guardrails for SocialPredict backend/API work. Use when touching backend Go files to enforce formatting, vet hygiene, and backend boundary-safe coding practices before review or verifier handoff.
Run `gocyclo` against SocialPredict Go code and summarize cyclomatic-complexity hotspots. Use when a user asks to check cyclomatic complexity, review complexity regressions, identify hard-to-maintain functions, or compare complexity before and after a backend refactor.
Run `gofmt` in check or write mode for SocialPredict Go code. Use when a user asks to check formatting drift, format backend Go files, or confirm `gofmt -l` passes before review or verifier handoff.
Run `golangci-lint` for SocialPredict backend Go code and summarize lint findings. Use when a user asks to run golangci-lint, wants a stricter lint pass than `go vet`, or needs a consolidated lint report before review or verifier handoff.