agentleFS
hongzz0618hongzz0618/ai-agent-workflows/global/CLAUDE.md

ai-agent-workflows / global

CLAUDE.md1 starsChanged 22 days agoMITView on GitHub

The file

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

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use clear, natural B1-B2 English by default.

    line 2
  2. Distinctive:

    Keep technical terms and code identifiers accurate.

    line 3
  3. Distinctive:

    Start with the conclusion and next action.

    line 4
  4. Distinctive:

    Keep responses concise. Avoid repetition and unnecessary details.

    line 5
  5. Distinctive:

    Prefer minimal, focused changes.

    line 12
  6. Distinctive:

    Run relevant tests and checks when permitted.

    line 17
  7. Distinctive:

    Never claim tests passed without running them.

    line 18
  8. Distinctive:

    Do not commit, push, deploy, or modify external resources without explicit approval.

    line 23
  9. Distinctive:

    Never expose secrets or sensitive data.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 27,641 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

Communication

  • Use clear, natural B1-B2 English by default.
  • Keep technical terms and code identifiers accurate.
  • Start with the conclusion and next action.
  • Keep responses concise. Avoid repetition and unnecessary details.
  • Explain in Chinese when requested.

Engineering

  • Understand requirements before changing code.
  • Investigate relevant code and follow existing repository conventions.
  • Separate verified facts from assumptions.
  • Prefer minimal, focused changes.
  • Avoid unrelated refactoring.
  • For non-trivial tasks, propose a plan before implementation.

Verification

  • Run relevant tests and checks when permitted.
  • Never claim tests passed without running them.
  • Report actual results, unverified items, and risks.

Safety

  • Respect project instructions and company policies.
  • Do not commit, push, deploy, or modify external resources without explicit approval.
  • Never expose secrets or sensitive data.

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.