How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
jarrodwattsCLAUDE.mdjarrodwatts/claude-hud/CLAUDE.md
line (`showTools`): ◐ Edit: auth.ts | ✓ Read ×3 - Skills/MCP lines (`showSkills` / `showMcp`): active Skill invocations and MCP servers; when the Skills line is enabled, Skill-tool entries are suppressed from the tools
alirezarezvaniCLAUDE.mdalirezarezvani/claude-skills/CLAUDE.md
# CLAUDE.md This file provides guidance to Claude Code (claude.ai/code) when working with code
alirezarezvaniCLAUDE.mdalirezarezvani/claude-skills/project-management/CLAUDE.md
grill-pm, /cs:pm-loop, /sprint-health, /project-health, /retro) **Key Feature:** Atlassian MCP Server integration for direct Jira/Confluence operations ## Orchestrator & Delivery Loop (pm-skills) `skills/pm-skills/` is the domain's `context: fork
activepiecesCLAUDE.mdactivepieces/activepieces/CLAUDE.md
Activepieces Open-source AI-first workflow automation platform. Self-hosted or cloud. 400+ pieces. MCP support. ## Architecture (Non-Obvious Rules) - **Multi-tenant**: Platform → Projects → Users. ALL queries MUST filter
SuperClaude-OrgCLAUDE.mdSuperClaude-Org/SuperClaude_Framework/CLAUDE.md
files) ├── skills/ # Installable skills (confidence-check, etc.) ├── hooks/ # Claude Code hook definitions ├── mcp/ # MCP server configurations (10 servers) └── core/ # Core utilities # Project Files tests/ # Python test suite (136 tests) ├── unit
microCLAUDE.mdmicro/go-micro/CLAUDE.md
RabbitMQ) ├── cache/ # Caching (Redis) ├── client/ # RPC client (gRPC) ├── cmd/micro/ # CLI tool (run, deploy, mcp, build, server) ├── codec/ # Message codecs (JSON, Proto) ├── config/ # Dynamic config (env, file, etcd, NATS) ├── errors/ # Error
czlonkowskiCLAUDE.mdczlonkowski/n8n-mcp/CLAUDE.md
typecheck # tsc --noEmit (npm run lint is an alias) # Running the server npm start # MCP server in stdio mode npm run start:http # MCP server in HTTP mode
claude-code-bestCLAUDE.mdclaude-code-best/claude-code/CLAUDE.md
DUMP_SYSTEM_PROMPT) - `--claude-in-chrome-mcp` / `--chrome-native-host` - `--computer-use-mcp` — 独立 MCP server 模式 - `--daemon-worker= ` — feature-gated (DAEMON) - `remote-control` / `rc` / `remote` / `sync` / `bridge` — feature-gated
steipeteCLAUDE.mdsteipete/CodexBar/docs/claude.md
explicit Refresh. - On Claude Code 2.1.x, `Claude Code-credentials` may contain only MCP server OAuth state (`mcpOAuth`) with no `claudeAiOauth`. CodexBar treats that as an OAuth configuration error, does
teng-linCLAUDE.mdteng-lin/notebooklm-py/CLAUDE.md
requires auth) uv run notebooklm --help # CLI ``` Always install the full extras set (`mcp`, `server`, `impersonate`); omitting them causes adapter suites to skip silently, masking errors and failing
getpaseoCLAUDE.mdgetpaseo/paseo/CLAUDE.md
Repository map This is an npm workspace monorepo: - `packages/server` — Daemon: agent lifecycle, WebSocket API, MCP server - `packages/app` — Mobile + web client (Expo) - `packages/cli` — Docker-style CLI (`paseo run/ls/logs/wait`) - `packages/relay` — E2E encrypted
AnthropicCLAUDE.mdanthropics/claude-quickstarts/managed-agents/assistant-ui/CLAUDE.md
create so the analyst remembers per-dataset conventions across chats. - **MCP connector**: add an `mcp_servers` entry plus an `mcp_toolset`. MCP tools default to `always_ask`, so they light
AnthropicCLAUDE.mdanthropics/claude-quickstarts/managed-agents/chat-sdk/CLAUDE.md
repo from the inside (`resources: [{type: "github_repository", ...}]`) - **MCP tools**: wire an external data MCP server (`mcp_servers` + `mcp_toolset` on the agent, credentials via a vault, `vault
AnthropicCLAUDE.mdanthropics/claude-quickstarts/managed-agents/daily-brief/CLAUDE.md
with `curl` and a vault-substituted `$SLACK_BOT_TOKEN`, and reads GitHub through the MCP server with a read-only token from the same vault. ``` cron (deployment.md) ──▶ session ──▶ agent.md
AnthropicCLAUDE.mdanthropics/claude-quickstarts/managed-agents/linear/CLAUDE.md
tools**: e.g. Linear or GitHub MCP so the agent can act, not only reply (`mcp_servers` + `mcp_toolset` in `agents/linear-assistant.md`, a `vaults/ .yaml` for the credential, which `ant apply` manages
AnthropicCLAUDE.mdanthropics/claude-quickstarts/managed-agents/mcp-server-typescript/CLAUDE.md
MCP server (TypeScript) × Claude Managed Agents MCP server that exposes Managed Agents session primitives as tools. Two entrypoints sharing one tool set: `src/server.ts` (stdio → Claude Desktop and Claude Code
AnthropicCLAUDE.mdanthropics/claude-quickstarts/managed-agents/slack/CLAUDE.md
tools**: e.g. Slack or GitHub MCP so the agent can act, not only reply (`mcp_servers` + `mcp_toolset` in `agents/slack-assistant.md`, a `vaults/ .yaml` for the credential, which `ant apply` manages
ag-ui-protocolCLAUDE.mdag-ui-protocol/ag-ui/CLAUDE.md
affected`) instead of using the underlying tooling directly - You have access to the Nx MCP server and its tools, use them to help the user - When answering questions about
open-metadataCLAUDE.mdopen-metadata/OpenMetadata/CLAUDE.md
operator/` — Kubernetes operator - `openmetadata-integration-tests/` — backend API integration tests (`*IT.java`) - `openmetadata-mcp/` — MCP server - `openmetadata-ui-core-components/` — canonical React component library - `openmetadata-ui/src/main/resources/ui/` — React frontend application - `openmetadata
yusufkaraaslanCLAUDE.mdyusufkaraaslan/Skill_Seekers/CLAUDE.md
context-local (a `ContextVar` layered over the unchanged base singleton) — thread/async safe for the MCP server; propagate to worker threads via `copy_context`. ### Standalone subsystems (outside `cli/`) Four top-level
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.
