CLAUDE.md

1# apps/web — Claude context
2 
3Next.js 16 frontend (`@medlens/web`).
4 
5## Commands
6 
7```bash
8pnpm --filter @medlens/web dev
9pnpm --filter @medlens/web lint
10pnpm --filter @medlens/web typecheck
11pnpm --filter @medlens/web test:unit
12pnpm --filter @medlens/web test:integration
13pnpm --filter @medlens/web build
14```
15 
16## Layout
17 
18- `src/app/` — App Router pages and layouts
19- `src/app/(marketing)/` — Public marketing routes (home, features, blog, glossary, etc.)
20- `src/components/ui/` — shadcn-style primitives
21- `src/components/marketing/` — Marketing section components
22- `src/content/data/` — JSON content (CMS-ready)
23- `src/lib/seo/`, `src/lib/analytics/`, `src/lib/content/` — SEO, GTM, content loaders
24- `src/tests/unit/` — Vitest unit tests
25- `src/tests/integration/` — integration tests
26- Shared types: `@medlens/types` from `packages/types`
27- Shared logger: `@medlens/logger` from `packages/logger`
28 
29## Conventions
30 
31- Server Components by default; `"use client"` only when needed.
32- Marketing copy lives in JSON under `src/content/data/` — edit JSON, not components, for content changes.
33- No medical interpretation logic in the UI — API owns clinical semantics.
34- Accessible markup; no PII in client logs or analytics events.
35- GTM loads only after analytics consent (`ConsentBanner`).
36 
37## Guidance for agents
38 
39- Treat this app as a Next.js project and follow the official Next.js and App Router guidance for routing, server/client boundaries, and performance.
40- When editing UI, review the official React and Next.js documentation for patterns before introducing new abstractions.
41- Prefer the official package documentation for any shared libraries used here (for example, Radix UI, Tailwind, and Vitest) over ad hoc implementation choices.
42- Keep the web experience consistent with the mobile and API apps by reusing shared contracts and package conventions.
43 
44## Skills by surface
45 
46**In-app UI:** `product-ux`, `web-frontend`, `ui-accessibility`, `web-performance`
47 
48**Marketing / public:** `product-ux`, `marketing-ui`, `technical-seo`, `content-seo`, `answer-engine-optimization`, `web-performance`, `analytics-tagging`, `ui-accessibility`
49 
50**Always:** `safety-privacy` for health copy and tracking
51 
52Commands: `/ui-audit`, `/perf-review` · Map: `docs/00-start/03-RULES_AND_SKILLS_MAP.md`
53