Files
digital-psychology/CLAUDE.md
T
jackyu66gitandCursor 19d3cd5945 refactor(ECR-001): 接入 ESS 并完成结构对齐 Phase A–E
绑定 ESS 双轨治理,拆分超大 H5 页与 Go 引擎,抽出 membership 服务,
并将 star/fortune 重命名为 outlook(JSON 双写兼容);同时修复 /psy API 代理与首页 + 菜单层级。

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-08-05 17:51:40 +08:00

2.5 KiB
Raw Blame History

CLAUDE.md

愈心谷 is an AI-first Monorepo. Treat .ai/ as the executable engineering system.

On every task

  1. Read AGENTS.md (load order is authoritative).
  2. Especially: .ai/ai-contract.md, constitution.md, architecture.md, domain.md, forbidden.md.
  3. Competitor parity / reverse engineering: .ai/design/reverse-engineering-spec.md (not a short prompt — full STEP 118).
  4. Prefer patterns/ + examples/ + playbooks/ over free-form invention.
  5. Finish with Review + DoD + matching checklist.

Layout

Path Role
.ai/ AI Engineering System (source of truth for rules)
apps/api Go API
apps/user-h5 Vue3 user H5
apps/mini-program Mini-program scaffold
packages/* sdk / types / utils / ui
apps/docs/ Human PRD / business docs (not a substitute for .ai/)
docs/ ESS process artifactsECR / TASK / HANDOFF / PROFILE

ESSprocess overlay

Bound to engineering-spec-system v1.0. Product rules stay in .ai/; change control uses ESS roles + docs/.

Load Agent Profile: ARCHITECT | ENGINEER | REVIEWER | RELEASE_MANAGER
  1. $ESS_ROOT/SKILL.md + $ESS_ROOT/agents/<PROFILE>.md
  2. docs/PROJECT_PROFILE.md · PROJECT_RULES.md · TECH_STACK.md
  3. Active docs/TASKS/ · docs/ECR/ · docs/HANDOFF/ · docs/STATE/
  4. Still obey AGENTS.md .ai/ load order for domain / Feature Spec / DoD
python scripts/ess-validate.py --phase design --ecr ECR-xxx
python scripts/ess-gate-check.py --ecr ECR-xxx

Do not copy the ESS tree into this repo. Architect must not edit apps/ / packages/.

Commands

export GOPROXY=https://goproxy.cn,direct   # if needed
cd apps/api && go run ./cmd/server
npm install && npm run dev:h5

Legacy

Static prototype (yuxingu.html / pages/ / css/ / js/) removed from tree — do not recreate. server.py must not grow product APIs. See LEGACY.md.

Skill routing

When the user's request matches an available skill, invoke it. When in doubt, invoke the skill.

  • Product ideas/brainstorming → /office-hours
  • Strategy/scope → /plan-ceo-review
  • Architecture → /plan-eng-review
  • Design → /design-consultation or /plan-design-review
  • Full review pipeline → /autoplan
  • Bugs/errors → /investigate
  • QA → /qa or /qa-only
  • Code review → /review
  • Ship/PR → /ship or /land-and-deploy
  • Save/resume context → /context-save / /context-restore
  • Spec/issue → /spec