# CLAUDE.md

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

## On every task

1. Read [AGENTS.md](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 1–18).
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 artifacts（ECR / TASK / HANDOFF / PROFILE） |

## ESS（process overlay）

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

```text
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](AGENTS.md) `.ai/` load order for domain / Feature Spec / DoD

```bash
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

```bash
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](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`