agentleFS
apacheapache/streampipes/CLAUDE.md

streampipes

CLAUDE.md756 starsChanged 52 days agoApache-2.0View on GitHub

Every directory with its own AGENTS.md also has a one-line CLAUDE.md containing @AGENTS.md, so the module guide loads automatically when you work inside that directory. The "Guide index" at the end of AGENTS.md lists them. If a task spans a module you have not touched yet, read its AGENTS.md before editing — the recipes (how to add a migration, an endpoint, an extension) and module-specific rules live there, not here. - security-triage — use when the task is to assess,…

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

3 rules. About 0 are common, 1 is distinctive, and 2 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.

  • 2

    Very specific

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

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

    Every directory with its own AGENTS.md also has a one-line CLAUDE.md containing @AGENTS.md, so the module guide loads automatically when …

    line 7
  2. Very specific:

    Run mvn -pl <module> -am test for the fast loop and mvn clean verify from the root before declaring backend work done.

    line 21
  3. Distinctive:

    Do not commit; leave changes in the working tree unless asked.

    line 24

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

Claude Code guide

@AGENTS.md

Nested guides

Every directory with its own AGENTS.md also has a one-line CLAUDE.md containing @AGENTS.md, so the module guide loads automatically when you work inside that directory. The "Guide index" at the end of AGENTS.md lists them. If a task spans a module you have not touched yet, read its AGENTS.md before editing — the recipes (how to add a migration, an endpoint, an extension) and module-specific rules live there, not here.

Skills

  • security-triage — use when the task is to assess, reproduce or report a suspected vulnerability. It loads THREAT_MODEL.md and the triage procedure. Do not load it for ordinary feature or bug work.

Working in this repository

  • Run mvn -pl <module> -am test for the fast loop and mvn clean verify from the root before declaring backend work done; only the root verify runs the license-header check.
  • For ui/ changes run npm run format && npm run lint && npm run i18n:check in ui/.
  • Do not commit; leave changes in the working tree unless asked.

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.