agentleFS
Sign inStart free
CodeWithBehnamCodeWithBehnam/cc-docs/CLAUDE.md

cc-docs

CLAUDE.md2 starsChanged 8 months agoMITView on GitHub

Official Claude Code documentation and reusable assets, downloaded from <https://code.claude.com/docs>. NEVER use em-dashes ('--') in generated text - they break formatting consistency. Use commas, periods, parentheses, or regular hyphens instead. ALWAYS update both CLAUDE.md and DOCUMENT-INDEX.md when docs are added, removed, or renamed - stale indexes cause agents to reference nonexistent files. ALWAYS commit and push after making changes - this is a shared documentation repo. ALWAYS use files in templates/ as starting points when creating any Claude Code feature…

We split this CLAUDE.md into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    NEVER use em-dashes ('--') in generated text - they break formatting consistency.

    line 33
  2. Distinctive:

    ALWAYS update both CLAUDE.md and DOCUMENT-INDEX.md when docs are added, removed, or renamed - stale indexes cause agents to reference …

    line 35
  3. Distinctive:

    ALWAYS commit and push after making changes - this is a shared documentation repo.

    line 37
  4. Very specific:

    ALWAYS use files in templates/ as starting points when creating any Claude Code feature - they contain tested patterns and correct …

    line 39
  5. Very specific:

    Update DOCUMENT-INDEX.md with any added, removed, or renamed files

    line 45
  6. Distinctive:

    Update the Architecture section above if counts or categories changed

    line 46
  7. Very specific:

    Read DOCUMENT-INDEX.md for the full file-by-file index.

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

Project: cc-docs

Official Claude Code documentation and reusable assets, downloaded from https://code.claude.com/docs.

Architecture

claude-code-docs/    # 45 official doc pages (getting started, usage, extensibility, IDE, CI/CD, cloud, enterprise, reference)
cheatsheets/         # 65 condensed cheatsheets per doc topic (quickstart, hooks, permissions, MCP, etc.)
templates/           # Copy-paste starting points (skills, subagents, hooks, CLAUDE.md starters, CI/CD, MCP, plugins)
rules/               # 8 drop-in path-specific rules (TypeScript, Python, React, Go, Rails, Rust, SQL, testing)
tips/                # 6 practical tip files + README
skills/              # 15 core + 222 community skills in 16 categories
commands/            # 12 core + 100 community slash commands in 12 categories
hooks/               # 10 core + community hook scripts
agents/              # 12 core + 185 community subagents in 14 categories
guides/              # 7 step-by-step workflow guides + README
output-styles/       # 11 response formatting styles + README
docs/brainstorms/    # Planning and brainstorm documents
Scripts/             # Maintenance scripts
awesome.md           # Curated resource list
DOCUMENT-INDEX.md    # Full file-by-file index (read this to find specific resources)

Commands

Scripts/download-cc-docs.sh      # Download/update docs from code.claude.com

Constraints

NEVER use em-dashes ('--') in generated text - they break formatting consistency. Use commas, periods, parentheses, or regular hyphens instead.

ALWAYS update both CLAUDE.md and DOCUMENT-INDEX.md when docs are added, removed, or renamed - stale indexes cause agents to reference nonexistent files.

ALWAYS commit and push after making changes - this is a shared documentation repo.

ALWAYS use files in templates/ as starting points when creating any Claude Code feature - they contain tested patterns and correct structure.

Updating Docs

  1. Run Scripts/download-cc-docs.sh
  2. Review new/changed/removed pages in claude-code-docs/
  3. Update DOCUMENT-INDEX.md with any added, removed, or renamed files
  4. Update the Architecture section above if counts or categories changed
  5. Commit and push

Finding Resources

Read DOCUMENT-INDEX.md for the full file-by-file index. Key entry points:

  • Templates: templates/SKILL-TEMPLATE.md, SUBAGENT-TEMPLATE.md, HOOKS-TEMPLATE.md, HOOKS-RECIPES.md
  • Language starters: Python, TypeScript, React, Rails, and monorepo CLAUDE.md starters in templates/
  • Cheatsheets: Quick-reference versions of every doc topic in cheatsheets/

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free