AWSCLAUDE.mdaws-cdk
aws/aws-cdk/CLAUDE.md
No summary in the file. Open it to read it.
CLAUDE.md examples from real projects
How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
Most stars firstWorked for most · soon
AWSCLAUDE.mdAWSCLAUDE.mdsagemaker-python-sdk
aws/sagemaker-python-sdk/CLAUDE.md
Guidance for Claude Code working in this repository — the source of the Amazon SageMaker Python SDK. This repository follows the AGENTS.md convention. To keep a single source of truth and avoid the two files drifting apart, all guidance lives in AGENTS.md and is imported here: For the full guidance — project context, the v3-by-default golden rule, banned v2 patterns and their v3 replacements, the SDK-first interface map, the contributing workflow, and a canonical v3 train + deploy example —…
AWSCLAUDE.mdaws-lambda-dotnet / Amazon.Lambda.DurableExecution
aws/aws-lambda-dotnet/Libraries/src/Amazon.Lambda.DurableExecution/CLAUDE.md
Amazon.Lambda.DurableExecution is the .NET SDK (GA, 1.x) for resilient, long-running AWS Lambda workflows that checkpoint progress after each step and resume after failures or waits. A workflow can run for up to ~1 year (the WAIT cap is 31,622,400 seconds) and is only billed for active compute. The SDK is client-side glue: the durable execution service (part of Lambda) owns the checkpoint store, fires timers, and re-invokes the function; this library re-derives in-memory workflow position from the checkpoint history the…
AWSCLAUDE.mdagentcore-cli
aws/agentcore-cli/CLAUDE.md
This project keeps all agent instructions in AGENTS.md files. Always follow the rules in ./AGENTS.md, and when working in subdirectories, also check for a closer AGENTS.md in that directory tree.
AWSCLAUDE.mdtools-for-devops-agent
aws/tools-for-devops-agent/.claude/CLAUDE.md
This repository consolidates open-source tools for AWS DevOps Agent — skills, custom agents, and MCP servers, plus supporting infrastructure templates. Follow these conventions when contributing. See CONTRIBUTING.md for the full contribution workflow. Skills live under skills/ and should follow both the Agent Skills spec best practices and AWS DevOps Agent best practices. Skills are the most common contribution type; the guidance below is the most detailed for that reason.
AWSCLAUDE.mdmodern-data-architecture-accelerator
aws/modern-data-architecture-accelerator/CLAUDE.md
See developer-code-review Operational guidance for commits, issues, MRs, reviews, and repo workflows See developer-operational-guidance Non-optional working requirements for all tasks See developer-working-requirements
AWSCLAUDE.mdn8n-nodes-agentcore
aws/n8n-nodes-agentcore/CLAUDE.md
This project keeps all agent instructions in AGENTS.md. Always follow the rules in ./AGENTS.md, and when working in subdirectories, also check for a closer AGENTS.md in that directory tree.
About CLAUDE.md
What is CLAUDE.md?
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
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.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.