agentleFS
Sign inStart free
patinaprojectpatinaproject/skills/CLAUDE.md

skills

CLAUDE.md1 starsChanged 20 days agoMITView on GitHub

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Keep the shared workflow contract in AGENTS.md.

    line 3
  2. Very specific:

    When you add Claude-specific teammates, prefer project subagents under .claude/agents/.

    line 5
  3. Very specific:

    When you need Claude-specific enforcement for teammate creation or completion, prefer project hooks in .claude/settings.json.

    line 6
  4. Very specific:

    Never write tests that assert on the prose content of documentation files.

    line 7

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

Claude Code

  • Keep the shared workflow contract in AGENTS.md; put Claude-only guidance below this import instead of duplicating the repo rules.
  • Project-level Claude Code configuration lives in .claude/settings.json. Skills enabled for this repo are declared under enabledPlugins.
  • When you add Claude-specific teammates, prefer project subagents under .claude/agents/.
  • When you need Claude-specific enforcement for teammate creation or completion, prefer project hooks in .claude/settings.json.
  • Never write tests that assert on the prose content of documentation files; test code behavior and machine-consumed contracts only (see AGENTS.md → Testing Guidelines and docs/adr/ADR-224-no-tests-on-documentation-content.md).

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