How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
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
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/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
paulrobelloCLAUDE.mdpaulrobello/claude-office/CLAUDE.md
make install # Install all dependencies make dev-tmux # Run in tmux (recommended) - backend :8000, frontend :3000 make dev-tmux-kill # Kill tmux session make checkall # Lint, typecheck, test all components
tony1223CLAUDE.mdtony1223/better-agent-terminal/CLAUDE.md
rust` - For local packaging verification without macOS signing/notarization: `pnpm run tauri:build:debug` ## Logging - **Frontend (renderer)**: Use `window.batAppAPI.debug.log(...)` instead of `console.log()`. This sends logs to the Tauri host logger, which
VikashLoombaCLAUDE.mdVikashLoomba/copilot-mcp/CLAUDE.md
string, command: string, args: string[], env: Record<string, string>, inputs: InstallConfigInput[] }, error?: string } ``` 3. **Frontend Processing**: - `SearchMCPServers` renders results immediately without CloudMCP details - Each `RepoCard` fetches its own CloudMCP details
MagicCubeCLAUDE.mdMagicCube/agentara/web/CLAUDE.md
Claude Code (claude.ai/code) when working with code in this repository. This is the frontend of Agentara (web/). See the parent ../CLAUDE.md and ../docs/overview.md for overall project context. ## Commands ```bash
HainrixzCLAUDE.mdHainrixz/the-architect/CLAUDE.md
Frame it as **"Here's what I'd build"** — not "here are your options." - Frontend in scope? Use `ui-ux-pro-max` for palette, type pairing and component style; `emil
fdmtlCLAUDE.mdfdmtl/director/CLAUDE.md
powered by better-auth. In development, we have two components: apps/studio which is the frontend. And apps/gateway that's the backend. You can start the frontend by running
saltboCLAUDE.mdsaltbo/agent-kanban/CLAUDE.md
while its inputs remain unchanged. The implementer may update both source and tests; a frontend edit alone does not require new E2E tests or a fixed sequence of specialist agents
duolahyperchoCLAUDE.mdduolahypercho/fusion-fable/CLAUDE.md
# Claude Fable 5 — System Prompt --- Claude should never use {antml:voice_note} blocks, even
antflydbCLAUDE.mdantflydb/antfly/CLAUDE.md
paths for provisioned, serverless, and embedded Lite deployments. ## Commands ```bash make build # All binaries + frontend + codegen make generate # After OpenAPI/proto changes (SDKs, docs, protobufs) ``` ## Testing **Zig tests and E2E suites
antflydbCLAUDE.mdantflydb/antfly/ts/CLAUDE.md
Agent Notes ## What this directory is TypeScript workspace for every Antfly frontend surface: the public SDK, unstyled search primitives, the shared design system, the graph widgets, the npm CLI wrappers
mudriiCLAUDE.mdmudrii/openclaw-dashboard/CLAUDE.md
Development Standards Zero-dependency Go HTTP server with embedded SPA frontend for OpenClaw bot metrics. ## Project Constraints - **Zero third-party dependencies** — `go.mod` has no `require` block, no `go.sum
HainrixzCLAUDE.mdHainrixz/open-carrusel/CLAUDE.md
Carrusel AI-powered Instagram carousel builder. Next.js 16 + React 19 + TypeScript + Tailwind v4. ## Architecture - **Frontend**: React app at localhost:3000 with chat panel (left), carousel preview (center), slide filmstrip (bottom
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.
