How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
kgoedeckeCLAUDE.mdkgoedecke/doop/CLAUDE.md
host via Docker: `docker compose up` (real Postgres, port 4400). ## Project layout ``` src/ - React frontend (Vite entry: index.html) src/components/ui/ - shadcn-generated UI primitives src/pages/ - route-level pages src/hooks/ - React hooks
alinaqiCLAUDE.mdalinaqi/maggy/templates/CLAUDE.md
summary like "all tests pass" without the output is a claim, not proof. 3. **Frontend / UI change → ALWAYS a screenshot.** If the change is visible in a UI, capture
sandbox-quantumCLAUDE.mdsandbox-quantum/switch/CLAUDE.md
level splits into three code trees: `core/` (backend package + tests), `gateway/` (operator dashboard frontend), and `console/` (desktop app). **Module layout:** - `config.py` — Pydantic `BaseSettings`; all config from environment variables - `db/` — Database
nateherkaiCLAUDE.mdnateherkai/token-dashboard/CLAUDE.md
token_dashboard/scanner.py` → `~/.claude/token-dashboard.db` (SQLite) - `token_dashboard/server.py` exposes JSON APIs (`/api/*`) + SSE stream (`/api/stream`) + static frontend (`web/`) - `web/` is vanilla JS, no build step — hash router + ECharts ## Data source Claude Code
henrydaumCLAUDE.mdhenrydaum/second-brain/CLAUDE.md
Second Brain — Architecture Notes Local-first AI kernel with SQLite persistence, a REPL frontend, package install/uninstall, and live plugin loading. Python / SQLite. Solo dev (Henry). The Flet GUI was removed
innocommerceCLAUDE.mdinnocommerce/innoshop/CLAUDE.md
cache:clear php artisan config:clear php artisan route:clear php artisan view:clear ``` ### Frontend Assets (Laravel Mix) ```bash # Install dependencies npm install # Development builds npm run dev # Build once
swarmclawaiCLAUDE.mdswarmclawai/swarmclaw/CLAUDE.md
working — whether by user verification, live agent testing, or manual QA — add regression tests (frontend and/or backend as appropriate) to prevent it from breaking later. The goal is to ratchet
marc-shadeCLAUDE.mdmarc-shade/world-intel-mcp/CLAUDE.md
Dashboard** (`dashboard/`): Self-contained Starlette app with a single `index.html` template (no frontend build step). SSE endpoint streams all domains in parallel via `asyncio.gather()`, refreshes every 30 seconds. Loads
samvallad33CLAUDE.mdsamvallad33/vestige/CLAUDE.md
check -p vestige-mcp` before commits that touch dashboard HTTP routes or MCP tools — frontend gates do not compile Rust. For documentation-only changes, at minimum run: ```sh git diff
SixHqCLAUDE.mdSixHq/Overture/CLAUDE.md
workspaces monorepo with two packages: - `packages/mcp-server` - The MCP server (Node.js/TypeScript) - `packages/ui` - The React frontend (React Flow + Zustand + Tailwind) ## Build & Development Commands ```bash # Install dependencies (from root) npm install # Development
djydeCLAUDE.mddjyde/ccmate/CLAUDE.md
backup various Claude Code configuration files across different locations (user, enterprise). ## Tech Stack - **Frontend**: React 19 with TypeScript - **Backend**: Rust with Tauri v2 - **Build Tool**: Vite with React plugin - **Styling
danielealbanoCLAUDE.mddanielealbano/android-remote-control-mcp/CLAUDE.md
leave stale published numbers after a detection-logic change. There are ZERO exceptions. --- ## 8) Frontend Rules (Jetpack Compose + Material Design 3) ### UI/UX baseline - Build modern, stylish, cool, responsive UI using
dbt-labsCLAUDE.mddbt-labs/dbt-mcp/CLAUDE.md
Pydantic model - Register matching resource with `@dbt_mcp.resource(uri=..., mime_type="text/html;profile=mcp-app")` - Frontend uses `@modelcontextprotocol/ext-apps` SDK ## Commands - `task test:unit` — run unit tests - `task test:integration` — run integration
rome-osCLAUDE.mdrome-os/rome/CLAUDE.md
container does not watch (`package.json`, container env), run `docker compose restart `. - When doing frontend-only work in `packages/web`, use `pnpm start:web:mock`. - When verifying a change, run `pnpm typecheck
rome-osCLAUDE.mdrome-os/rome/rome_apps/CLAUDE.md
when* to ship, read [`app_creation/AUTHORING.md`](coding/src/skills/app_creation/AUTHORING.md) — the iteration loop, product-design rules, frontend and icon guidelines, the recurring-run pattern, boundaries, validation, and the delivery checklist. - When you need
FerroxLabsCLAUDE.mdFerroxLabs/wayland/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
zhsamaCLAUDE.mdzhsama/claude-sub-agent/CLAUDE.md
claude/agents/ cp commands/agent-workflow.md .claude/commands/ # Organize agent files (current reorganization in progress) # Backend agents: agents/backend/ # Frontend agents: agents/frontend/ # Spec workflow agents: agents/spec-agents/ # UI/UX agents: agents/ui-ux/ # Utility agents: agents/utility/ ``` ## System Architecture ### Multi
biaogebusyCLAUDE.mdbiaogebusy/web-builder/CLAUDE.md
docroot/modules/custom/xinshi_api/` plus deployment-specific deltas. The dev proxy target `base.builder.design` serves this codebase. ## Sibling Frontend Repository - `../pro` — the pro deployment checkout of this frontend (branch `pro`). It merges `master
gglucassCLAUDE.mdgglucass/headroom-desktop/CLAUDE.md
plus `cargo check --manifest-path src-tauri/Cargo.toml` if the change crosses module boundaries. - Frontend changes: `npx tsc --noEmit` and any relevant Vitest suite. For visual changes, see Styling Rules
VercelCLAUDE.mdvercel/workflow-examples/custom-adapter/CLAUDE.md
Use Bun instead of Node.js, npm, pnpm, or vite.
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.
