How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
AnthropicCLAUDE.mdanthropics/claude-quickstarts/managed-agents/daily-brief/CLAUDE.md
Daily brief on Claude Managed Agents A scheduled deployment, not an app: there is no long-running process in this quickstart. `agents/daily-brief/` holds six resource files that `ant apply` reconciles
AnthropicCLAUDE.mdanthropics/claude-quickstarts/managed-agents/mcp-server-typescript/CLAUDE.md
which client they're targeting (Claude Desktop or Claude Code → stdio path, claude.ai → HTTP + deploy + connector), then follow that path's checklist. Both end with the same `send_message → wait
AnthropicCLAUDE.mdanthropics/claude-quickstarts/managed-agents/self-hosted-sandboxes/CLAUDE.md
first by every directory below. Each provider's README is its own runbook: setup, deploy, register the `session.status_run_started` webhook in the Console, test. Their environment key and webhook
AnthropicCLAUDE.mdanthropics/claude-quickstarts/managed-agents/sentry/CLAUDE.md
Sentry triage × Claude Managed Agents Scheduled deployment: cron → Managed Agents session with `sentry-cli` and a vault env-var credential → triage report in `/mnt/session/outputs/`. ## When the user asks
triggerdotdevCLAUDE.mdtriggerdotdev/trigger.dev/docs/CLAUDE.md
json` ## Directory Structure - `documentation/` - Core conceptual docs - `guides/` - How-to guides - `config/` - Configuration reference - `deployment/` - Deployment guides - `tasks/` - Task documentation - `realtime/` - Real-time features - `runs/` - Run management - `images/` - Image assets
chenhg5CLAUDE.mdchenhg5/cc-connect/CLAUDE.md
agent.(AgentDoctorInfo); ok { bin = info.CLIBinaryName() } ``` ### 3. Configuration Over Code - Features that may vary per deployment should be configurable in `config.toml` - Use `map[string]any` options for agent/platform factories to stay
open-metadataCLAUDE.mdopen-metadata/OpenMetadata/CLAUDE.md
trees: `ingestion/` (Python framework + connectors), `bootstrap/sql/` (DB migrations), `conf/` (configuration), `docker/` (local + prod deployment). ## Hard cross-cutting constraints (apply to every session, all languages) **Secrets & security.** Never commit secrets
coleam00CLAUDE.mdcoleam00/context-engineering-intro/claude-code-full-guide/CLAUDE.md
find -name' for better performance", ), ``` ## 🚀 GitHub Flow Workflow Summary main (protected) ←── PR ←── feature/your-feature ↓ ↑ deploy development ### Daily Workflow: 1. git checkout main && git pull origin main 2. git checkout -b feature/new-feature
Orchestra-ResearchCLAUDE.mdOrchestra-Research/AI-Research-SKILLs/CLAUDE.md
experimental verification, covering the full lifecycle: literature survey, ideation, dataset preparation, training pipelines, model deployment, evaluation, and paper writing. ## Repository Architecture ### Directory Structure (98 Skills Across 23 Categories) Skills
omnigent-aiCLAUDE.mdomnigent-ai/omnigent/.github/triage_v2/CLAUDE.md
Declarative Automation Bundles Project This project uses Declarative Automation Bundles for deployment. ## Prerequisites Install the Databricks CLI 0.292.0 or newer and verify with `databricks -v`. ## For AI Agents Read
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.
