How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
alirezarezvaniCLAUDE.mdalirezarezvani/claude-skills/engineering-team/CLAUDE.md
architect** — Azure infrastructure design, ARM/Bicep templates, landing zones - **gcp-cloud-architect** — GCP infrastructure design, Terraform modules, cloud-native patterns - **security-pen-testing** — Penetration testing methodology, vulnerability assessment, exploit analysis - **snowflake
antonbabenkoCLAUDE.mdantonbabenko/terraform-skill/CLAUDE.md
generated from `SKILL.md`, so the skill content is shared, not forked. ## Repository Structure ``` terraform-skill/ ├── skills/ │ └── terraform-skill/ # Skill autodiscovered by Claude Code plugin system │ ├── SKILL.md # Core skill file
daymadeCLAUDE.mddaymade/claude-code-skills/CLAUDE.md
# CLAUDE.md This file provides guidance to Claude Code (claude.ai/code) when working with code
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.
