Context Map

This monorepo contains multiple workspaces, each with its own domain concerns. CONTEXT.md files live alongside each workspace.

Workspaces

Workspace	Description	Context file
app/	Frontend SPA (React + Vite + shadcn/ui)	app/CONTEXT.md
workers/	Active backend (Cloudflare Workers + D1)	workers/CONTEXT.md

How to use

• Start here to discover which context is relevant to your task.
• Read the specific CONTEXT.md for domain vocabulary, entities, and business rules.
• Cross-cutting specifications in docs/product/prd.md, docs/architecture/srs.md, docs/architecture/sdd.md.
• Past architectural decisions in docs/architecture/adr/.

Navigation flow between contexts

1. Frontend task → app/CONTEXT.md → entities, business rules, key app files.
2. Backend task → workers/CONTEXT.md → entities, API routes, business rules, key worker files.
3. Cross-cutting task → docs/product/prd.md (product), docs/architecture/srs.md (requirements), docs/architecture/sdd.md (design), docs/architecture/adr/ (decisions).

Conventions

• Each workspace maintains its own CONTEXT.md as the source of truth for that context.
• The Context Map (this file) is the entry point for locating information.
• Generated documentation (VitePress) mirrors this structure in docs/.

---

Source: CONTEXT-MAP.md