text-based formats. It features a Django/GraphQL backend with PostgreSQL + pgvector, a React/TypeScript frontend with Jotai state management, and pluggable document processing pipelines powered by machine learning models.
## Baseline Commit
Frontend Design Language
## Design Philosophy
The design system emphasizes clarity, depth, and delight through subtle animations and thoughtful visual hierarchy.
## Core Design Principles
### 1. Visual Hierarchy Through Depth
- **Layered Cards
hand-authored datasets.
A `uv` workspace (`backend`, `workers`, `sdk`) plus a pnpm Next.js app (`frontend`) and a Nextra docs site (`docs`).
## Commands
```bash
make install # uv sync --all-packages
with perf HUD (VITE_HELMOR_PERF_HUD=1)
bun run build # tsc + vite build (frontend bundle to dist/)
bun run typecheck # tsc --noEmit for frontend AND sidecar
bun run lint
based client built as a CLI tool serving a Vite application.
**Core Architecture**:
- Frontend: Vite + TanStack Router + React 19 + TanStack Query
- Backend: Hono (standalone server) + Effect-TS (all business logic
repository.
Zen is a self-hosted notes app: Go backend with SQLite (FTS5), Preact frontend bundled by esbuild.
## Core rules (always apply)
- Keep code simple and readable; prefer the smallest
site-architecture`, `programmatic-seo`, or `schema` skill based on the task.
- Use the `anthropic-frontend-design` or `openai-frontend-design` skill when creating or reshaping a UI.
## MCP Tools
### Tavily
endpoints belong in `turbo/apps/api` (Hono,
`src/signals/routes/`). Browser clients call the canonical API service.
Frontend apps must not add API handlers or thin proxy handlers. If a frontend
origin must expose
split PRs:**
- **Multiple unrelated behaviors** (authentication vs database vs caching)
- **Different deployment boundaries** (frontend vs backend in systems with separate deployment pipelines)
- **Refactoring separate from new features** (clean up existing
herdr plugin install`, the operator's only other way to refresh
([ADR 0006](./.adr/0006-update-advances-the-checkout-herdr-installed.md)).
- **Frontend changes** (`web/`): rebuild with `bun run build` (root) or `cd web && bun run build
exist, but you can still run the script if `echo $MORPH_API_KEY` works.
# Frontend
This project uses React, TanStack Router, TanStack Query, Shadcn UI, and Tailwind CSS.
Always
prohibited.
New interactive controls must come with the matching i18n entries: `apps/web/src/i18n.js` (frontend) or `packages/app/server/i18n.js` (server/CLI) — adding them to the wrong file is prohibited.
After any code change, `pnpm
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.