How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
SixHqCLAUDE.mdSixHq/Overture/CLAUDE.md
Monorepo Structure This is an npm 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
djydeCLAUDE.mddjyde/ccmate/CLAUDE.md
Package Manager**: pnpm (required) ## Development Commands ```bash # Install dependencies pnpm install # Start development server pnpm tauri dev # Build for production pnpm build # Preview built app pnpm preview # Check TypeScript lint
tuannvmCLAUDE.mdtuannvm/codex-mcp-server/CLAUDE.md
Codex CLI ``` ### Key Files | File | Purpose | |------|---------| | `src/index.ts` | Entry point, creates and starts `CodexMcpServer` | | `src/server.ts` | MCP server setup, handles `list_tools` and `call_tool` requests | | `src/tools/definitions.ts` | MCP tool schemas (input/output
emiliaprotocolCLAUDE.mdemiliaprotocol/emilia-protocol/CLAUDE.md
claiming what they show): examples/ (e.g. examples/scitt/capsule-seam-vector-v2.mjs, examples/wimse-pep/, examples/external-verification/) - Gate (productized enforcement point): packages/gate - MCP server: mcp-server/ - Capability map: docs/CAPABILITY-MAP.md - Repository disclosure boundary: docs/REPOSITORY-BOUNDARIES.md
ee0pdtCLAUDE.mdee0pdt/Godot-MCP/CLAUDE.md
CLAUDE.md - Godot MCP Project Guidelines ## Build & Run Commands - **Server Build**: `cd server && npm run build` - **Server Start**: `cd server && npm run start` - **Server Dev Mode**: `cd server
dbt-labsCLAUDE.mddbt-labs/dbt-mcp/CLAUDE.md
tool_names) - Tool categories: `discovery/`, `semantic_layer/`, `dbt_cli/`, `dbt_codegen/`, `dbt_admin/`, `lsp/`, `mcp_server_metadata/` - Prompts (tool descriptions): `src/dbt_mcp/prompts/` - Config: `src/dbt_mcp/config/` - Tests: `tests/unit/`, `tests/integration/` ## Tool Architecture Tools follow
alpbahadurCLAUDE.mdalpbahadur/49-IDE/CLAUDE.md
HTML files reference .min.js versions so this must be done before restarting the cloud server. REBUILDING AGENT TARBALL: After changing any agent code (agent/src/, agent/services/, agent/bin/), rebuild the tarball that
xianyu110CLAUDE.mdxianyu110/awesome-claudcode-tutorial/CLAUDE.md
三种模式详解 ├── 05-terminal-commands.md # 终端命令执行 ├── 06-plan-mode.md # 规划模式 ├── 07-permissions.md # 权限管理 ├── 08-background-tasks.md # 后台任务 ├── 09-rewind.md # 版本回滚 ├── 10-image-processing.md # 图片处理 ├── 11-mcp-setup.md # MCP Server 安装 ├── 12-resume.md # 恢复历史会话 ├── 13-mcp-design.md # MCP 还原设计稿 ├── 14-context-management.md # 上下文管理 ├── 15-claude-md.md # CLAUDE.md 项目记忆 ├── 16-hooks.md # Hook 系统
aitytechCLAUDE.mdaitytech/agentkits-marketing/CLAUDE.md
management & coordination - `copywriter` - Content creation & messaging - `docs-manager` - Marketing documentation & brand guidelines - `mcp-manager` - MCP server integrations & tool orchestration ### Reviewer Agents (Quality Assurance) - `brand-voice-guardian` - Brand consistency and voice
anombyte93CLAUDE.mdanombyte93/prd-taskmaster/CLAUDE.md
lockstep: - `script.py` — thin shim over `prd_taskmaster/cli.py:main` (~40 subcommands; `python3 script.py -h`). - `mcp-server/server.py` — FastMCP server exposing the same ops as MCP tools (`next_task`, `set_task_status
FradSerCLAUDE.mdFradSer/dotclaude/marketing/CLAUDE.md
introw, composio - **Composio** (integration layer): Adds MCP access to OAuth-heavy tools without native MCP servers (HubSpot, Salesforce, Meta Ads, LinkedIn Ads, Google Sheets, Slack, etc.). See `tools/integrations/composio.md` ### Registry Structure
christopherkaraniCLAUDE.mdchristopherkarani/Swarm/CLAUDE.md
Tool, @Parameter, │ │ # @Traceable, #Prompt, builders) │ ├── SwarmMembrane/ # Deprecated hollow re-export (remove in 0.7.0) │ ├── SwarmMCP/ # MCP server adapter product │ ├── SwarmCapabilityShowcase/ # Executable: deterministic showcase CLI │ ├── SwarmCapabilityShowcaseSupport/ # Library backing the showcase │ ├── SwarmDemo
minhnv0807CLAUDE.mdminhnv0807/ai-business-skills/CLAUDE.md
luong [Kiem tra truoc khi giao] ``` ## MCP Ads Integration Khi user da ket noi MCP server cho nen tang quang cao, cac skill co the pull data tu dong thay
HelmiCLAUDE.mdHelmi/claude-simone/CLAUDE.md
same time this repository itself uses Simone to organize its own work (currently the mcp-server based version). ## Activity Logging You have access to the `log_activity` tool
HelmiCLAUDE.mdHelmi/claude-simone/mcp-server/CLAUDE.md
CLAUDE Instructions - MCP Server Development ## Overview This is the MCP (Model Context Protocol) server implementation for Simone. This is a complete rewrite of the legacy directory-based command system. ## Tech
slopusCLAUDE.mdslopus/happy-cli/CLAUDE.md
Mobile app → Server → Claude SDK → Server → Mobile app 4. **Permission Handling**: - Claude requests permission → MCP server intercepts → Sends to mobile → Mobile responds → MCP approves/denies ## Key Design Decisions 1. **File-based
fabio-rovaiCLAUDE.mdfabio-rovai/open-ontologies/CLAUDE.md
Claude adds them. The MCP tools are individual operations — Claude is the orchestrator. ## Tool Reference | Tool | When to use | | ---- | ----------- | | `onto_status` | To check if the server is running and healthy
nirholasCLAUDE.mdnirholas/XActions/CLAUDE.md
order: which lane to use (shell out to the `xactions` CLI, or load the MCP server), the CLI lane and its output contract, the MCP lane, a table from common
tzachbonCLAUDE.mdtzachbon/smart-ralph/CLAUDE.md
prompts - `/plugin-dev:hook-development` - Creating hooks (PreToolUse, PostToolUse, Stop, etc.) - `/plugin-dev:mcp-integration` - Integrating MCP servers into plugins - `/plugin-dev:plugin-settings` - Plugin configuration with .local.md files - `/plugin-dev:create-plugin` - Guided
anyprotoCLAUDE.mdanyproto/anytype-mcp/CLAUDE.md
MCP tools. ### Core Components **MCP Proxy Layer (`src/mcp/proxy.ts`)** - Central orchestrator that implements the MCP server protocol - Converts OpenAPI operations to MCP tools dynamically at runtime - Handles tool listing and execution
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.
