菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | socialpredict-design-plan |
| description | 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. |
lib/design/design-plan.schema.json before drafting or revising the design plan.lib/design/design-plan.json as the canonical writable artifact.open_questions, risks, and decision_log rather than hiding it in prose.lib/design/design-plan.json.lib/design/design-plan.schema.json.authors must identify the contributing agent and its design posture.decision_log should contain durable architectural or modeling decisions, not transient implementation notes.workstreams may exist at a design level, but they should remain objective-oriented and avoid ticket decomposition.lib/design/, not in .codex/skills/ and not in ad hoc root files.lib/design/design-plan.json defines the design output they share.lib/design/design-plan.schema.json: canonical JSON Schema for the design plan.lib/design/design-plan.json: canonical writable design-plan artifact.lib/design/README.md: rationale for why the plan lives in lib/.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.
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.