agentleFS
amplifthqamplifthq/openmeld/.claude/CLAUDE.md

openmeld

CLAUDE.md1.4k starsChanged 38 days agoMITView on GitHub

Read AGENTS.md first and follow it. It is the single agent-facing rule authority for this repository: production guardrails, context routing to developing/ owner documents, core invariants, task rules, testing gates, lane safety, and commit rules all live there. This file is a thin adapter and must stay one. Do not copy rules, routing tables, or architecture facts into it; change AGENTS.md or the owning developing/ document instead. Code standards live in developing/engineering/code-standards.md and are routed from AGENTS.md.

1 other project uses a version of this.

Trending

More talk lately.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: 0 mentionsSep 2026: 0 mentionsOct 2026: 24 mentionsNov 2026: 7 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the amplifthq/openmeld repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about amplifthq/openmeld

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

See all 31

Talked about on GitHub (31 times).

On GitHub · 31

26 more on GitHub

The file

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

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Read AGENTS.md first and follow it.

    line 3

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

Read AGENTS.md first and follow it. It is the single agent-facing rule authority for this repository: production guardrails, context routing to developing/ owner documents, core invariants, task rules, testing gates, lane safety, and commit rules all live there.

This file is a thin adapter and must stay one. Do not copy rules, routing tables, or architecture facts into it; change AGENTS.md or the owning developing/ document instead.

Code standards live in developing/engineering/code-standards.md and are routed from AGENTS.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.