How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
PackmindHubCLAUDE.mdPackmindHub/packmind/apps/CLAUDE.md
Categories ### Backend Services - **api** - Main NestJS backend API with hexagonal architecture, TypeORM, and BullMQ ### Frontend & CLI - **frontend** - React Router v8 SPA - **cli** - Command-line interface built with
PackmindHubCLAUDE.mdPackmindHub/packmind/CLAUDE.md
management - **Testing**: Jest with @swc/jest as test runner ## Directory Structure - `apps/` - Deployable applications (API, frontend, CLI, e2e tests, docs) - `packages/` - Reusable domain and infrastructure packages shared across apps - `.github/workflows/` - CI/CD
PackmindHubCLAUDE.mdPackmindHub/packmind/packages/CLAUDE.md
feature-flags** - Shared, browser-safe feature-flag registry and decision logic (consumed by both frontend and backend) - **playbook-change-applier** - Applies proposed changes to playbook artifacts (standards, commands, skills) ### Integration
ucsandmanCLAUDE.mducsandman/DashClaw/CLAUDE.md
visits required must be zero. 4. **Was it verified rendered?** Drive the actual page (frontend-verify skill / headless browser) and confirm the new element appears and its controls work
useagenthqCLAUDE.mduseagenthq/useagent/CLAUDE.md
this repository. Two standalone apps plus shared packages (no workspace/turbo; every package installs independently). - `frontend/` - Next.js + React product UI on the BoardUI design system. Conventions live in `frontend/AGENTS.md` and `frontend/components/foundations/DESIGN-RAMP.md
DatabricksCLAUDE.mddatabricks/tmm/OpenSky-Marketplace-Visualization/CLAUDE.md
built SPA is committed in `dist/`, so no Node build is required. (The Vite/React frontend source and the offline SQL pipeline live in the author's separate project
DatabricksCLAUDE.mddatabricks/tmm/Zerostream/CLAUDE.md
streams to Databricks Unity Catalog via ZeroBus. **Documentation**: https://docs.databricks.com/aws/en/ingestion/zerobus-ingest ## Architecture ``` Mobile Browser → Frontend App → ZeroBus → Delta Table → Backend App → Dashboard │ ├──► ZeroBus (Databricks SQL) │ └──► Lakebase (PostgreSQL) [via replication] ``` - **Frontend
theexperiencecompanyCLAUDE.mdtheexperiencecompany/gaia/CLAUDE.md
GAIA is a proactive personal AI assistant — full-stack Nx monorepo with a Next.js frontend, FastAPI/LangGraph backend, React Native mobile app, Electron desktop app, and Discord/Slack/Telegram bots. ## Engineering Discipline
zenml-ioCLAUDE.mdzenml-io/kitaru/docker/CLAUDE.md
release does not need an image rebuild; dependency and bundled-example changes do. The frontend selects the ECR tag from the workspace version, and existing Modal sandboxes do not update
zenml-ioCLAUDE.mdzenml-io/kitaru/docs/CLAUDE.md
Generation scripts — do not hand-edit or commit generated output | | `app/`, `components/`, `lib/` | Designer / frontend (layout, theme, routes, metadata) | | `global.css` | Designer (branding) | | `mdx-components.tsx` | Shared (component registration) | ## Cross-surface docs guidance
sudocode-aiCLAUDE.mdsudocode-ai/sudocode/.claude/CLAUDE.md
server (@sudocode-ai/mcp) - wraps CLI ├── server/ # Local backend (@sudocode-ai/local-server) - executions + API ├── frontend/ # React UI (@sudocode-ai/local-ui) - web interface ├── sudocode/ # Meta-package (bundles all) └── .sudocode/ # Example project
MadAppGangCLAUDE.mdMadAppGang/claude-code/CLAUDE.md
Claude Code **Owner:** Jack Rudenko (i@madappgang.com) @ MadAppGang **License:** MIT ## Plugins | Plugin | Version | Purpose | |--------|---------|---------| | **Frontend** | v3.15.1 | React/TypeScript dev with 11 agents, multi-model review | | **Code Analysis** | v3.2.2 | Codebase investigation with claudemem
ship-studioCLAUDE.mdship-studio/ship-studio/CLAUDE.md
Window management helpers ### AI Features - PR title/description generation using Claude CLI (`src-tauri/src/commands/ai.rs`) - Frontend wrapper in `src/lib/ai.ts` - Uses `find_claude_binary()` to locate Claude Code installation - Gathers git diff
KimYx0207CLAUDE.mdKimYx0207/Meta_Kim/CLAUDE.md
visible run-scoped worker labels may be coarse English role-family names such as `frontend`, `backend`, or `test`, but Meta_Kim does not project those execution labels as durable agents
shangyankejiCLAUDE.mdshangyankeji/super-dev/.claude/CLAUDE.md
next sequence is research -> three core documents -> wait for user confirmation -> Spec / tasks -> frontend first with runtime verification -> backend / tests / delivery. - In SEEAI mode, the next sequence is research -> compact
shangyankejiCLAUDE.mdshangyankeji/super-dev/CLAUDE.md
super_dev/creators/`) - `document_generator.py` — PRD, architecture, UIUX document generation - `prompt_generator.py` / `prompt_templates.py` — LLM prompt construction - `frontend_builder.py` — frontend implementation playbooks - `implementation_builder.py` — backend implementation references - `spec_builder.py` — spec generation from documents - `adr_generator.py` — Architecture Decision Record
tobilgCLAUDE.mdtobilg/ai-observer/CLAUDE.md
dependencies (go mod download + pnpm install) # Development make dev # Run both backend and frontend in dev mode (parallel) make backend-dev # Run only backend (go run ./cmd/server) make frontend
ilhamfpCLAUDE.mdilhamfp/pasal/CLAUDE.md
Always read the current function body before replacing. ## Brand & Design **Read `BRAND_GUIDELINES.md` before any frontend work.** Key rules: - **One accent color:** Verdigris `#2B6150` (`bg-primary`) — buttons, links, focus rings - **Background
speakeasy-apiCLAUDE.mdspeakeasy-api/gram/CLAUDE.md
framework/functions/`: TypeScript SDK for function authors (`Gram.tool()` API, manifest generation, MCP passthrough) - `client/`: Frontend React application for Gram. Gram Elements — a chat interface that integrates with Gram MCP servers
vakovalskiiCLAUDE.mdvakovalskii/codbash/CLAUDE.md
handoff.js Generate context documents for session handoff between agents changelog.js In-app changelog data frontend/ index.html HTML template with {{STYLES}} and {{SCRIPT}} placeholders styles.css All CSS including dark/light/monokai themes app.js
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
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 Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.
