agentleFS
pathintegral-institutepathintegral-institute/mcpm.sh/CLAUDE.md

mcpm.sh

CLAUDE.md1k starsChanged 19 months agoMITView on GitHub

This file contains conventions that Claude should follow when working on this project.

Trending

Steady talk.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 1 mentionSep 2026: 0 mentionsOct 2026: 1 mentionNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the pathintegral-institute/mcpm.sh repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about pathintegral-institute/mcpm.sh

The biggest 5 of 52 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 52

Talked about on GitHub, Hacker News and Bluesky (52 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 1

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Dependency Management: Use uv for all Python dependency management.

    line 5
  2. Very specific:

    Formatting: Always format Python code with ruff.

    line 7
  3. Distinctive:

    NEVER commit anything to git unless explicitly asked to do so.

    line 9
  4. Distinctive:

    Always double-check with the user before committing changes to git.

    line 10

≈ “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

Claude Project Conventions

This file contains conventions that Claude should follow when working on this project.

  • Dependency Management: Use uv for all Python dependency management.
  • Python Environment: You are in the uv .venv Python environment. All dependency code can be found in .venv/.
  • Formatting: Always format Python code with ruff.
  • Committing:
    • NEVER commit anything to git unless explicitly asked to do so.
    • Always double-check with the user before committing changes to git.
    • This project follows semantic release - commit messages MUST follow Conventional Commits format.
    • Examples: feat:, fix:, docs:, style:, refactor:, perf:, test:, chore:
    • BREAKING CHANGES: Adding BREAKING CHANGE: in the commit footer triggers a major release. This is very uncommon - NEVER do this unless explicitly told to do so.

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.