How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
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
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
avivlCLAUDE.mdavivl/claude-007-agents/CLAUDE.md
REST/GraphQL design patterns - `@graphql-architect` - Schema design, federation, subscriptions - `@backend-developer` - General backend architecture - `@frontend-developer` - UI/UX implementation - `@tailwind-css-expert` - Responsive design - `@developer-experience-optimizer` - Productivity, automation, tooling - `@legacy
MicrosoftCLAUDE.mdmicrosoft/Sico/frontend/CLAUDE.md
CLAUDE.md — frontend The canonical Sico frontend lives in `frontend/` inside the Sico monorepo. It is a pnpm + Turborepo workspace for the application and shared frontend packages. ## Stack React 19 + TypeScript
MicrosoftCLAUDE.mdmicrosoft/Sico/frontend/packages/app/CLAUDE.md
sico/app — CLAUDE.md Sico frontend application — TanStack Router file-based routing, Jotai state, react-query + axios data layer, zod validation. ## Commands `npm run dev` / `build` / `preview` / `lint` / `test` / `test:build
awattarCLAUDE.mdawattar/claude-code-best-practices/CLAUDE.md
multiple layers - **general-backend-developer** - API development, database patterns, and server-side logic - **general-frontend-developer** - UI/UX implementation, component patterns, and browser automation - **general-devops** - Infrastructure automation, CI/CD, container orchestration
tinyhumansaiCLAUDE.mdtinyhumansai/opencompany/CLAUDE.md
under `docs/` is short for `crates/opencompany-core/src/...`; the data the crate embeds and reads (`companies/`, `frontend/`, `vendor/`) stays at the repository root, `../..` from `CARGO_MANIFEST_DIR`. - `crates/opencompany-app`: the Tauri desktop shell
gluk-wCLAUDE.mdgluk-w/claworc/CLAUDE.md
agent. The project consists of the following components: * Control Plane (Golang backend and React frontend) with dashboard, VNC client for Chromium, Terminal, Logs and other useful stuff. * Agent image with
rohunjCLAUDE.mdrohunj/claude-build-workflow/CLAUDE.md
completable in one coding session 3. **Order**: Dependencies must come first (database → backend → frontend) 4. **Criteria**: Must be specific and verifiable, include "Typecheck passes" Fix any issues by: - Splitting large
Miosa-osaCLAUDE.mdMiosa-osa/canopy/CLAUDE.md
Owns | Touch | |-------|------|-------| | `@devops-engineer` | `canopy/` root, `docs/`, `.github/`, `packages/` | YES | | `@backend-elixir` | `backend/` | YES | | `@frontend-svelte` | `desktop/`, `src-tauri/` | YES | Do not modify files outside your ownership without explicit instruction
LKbabaCLAUDE.mdLKbaba/Claude-code-ChatInWindows/CLAUDE.md
HTML | `src/ui-v2/index.ts` | Assembles full HTML: CSP header + styles + body + script | | UI script | `src/ui-v2/ui-script.ts` | Entire frontend JS as a TypeScript template literal | | UI body | `src/ui-v2/getBodyContent.ts` | HTML body markup (settings panel, chat
LerianStudioCLAUDE.mdLerianStudio/ring/CLAUDE.md
Gate 0 per task, Gate 8/9 per epic, Step 11.5 phase boundary) | | Dev cycle frontend | `ring:running-dev-cycle-frontend` → rolling-wave phased cycle (Gate 0 per task, Gate
FerroxLabsCLAUDE.mdFerroxLabs/ijfw/CLAUDE.md
point. IJFW orchestrates think-build-ship end to end and dispatches peer specialist skills (frontend-design, TDD, code-review) as subagent tools when the workflow needs them
NicholasSpisakCLAUDE.mdNicholasSpisak/claude-code-subagents/CLAUDE.md
specifications ### Agent Categories **Technical Specialists:** - `backend-reliability-engineer`: Server-side systems, APIs, databases, microservices - `frontend-ux-specialist`: UI/UX components, accessibility, performance, mobile-first development - `systems-architect`: System design, scalability, architectural
lidge-aiCLAUDE.mdlidge-ai/cli-jaw/CLAUDE.md
After changing `server.ts`/`src/**`/`bin/**`, run `npm run build` before telling anyone to restart; frontend changes additionally need `npm run build:frontend`. Full rules: `AGENTS.md` § Build & Deploy Contract. ## Current Runtime
dmarcguardhqCLAUDE.mddmarcguardhq/parse-dmarc/CLAUDE.md
assistant integration. ## Tech Stack - **Backend**: Go 1.25.4 (see go.mod for exact version) - **Frontend**: Vue.js 3 with Vite - **Database**: SQLite (supports both CGO and pure-Go variants) - **Package Manager
Idun-GroupCLAUDE.mdIdun-Group/idun-agent-platform/CLAUDE.md
Mypy. - Schema changes land in `idun_agent_schema` first, then engine and standalone consumers. Frontend types regenerate from the standalone OpenAPI spec. ## Coding Guidelines — Severity Matrix (auto-generated) | ID | Title
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.
