agentleFS
gustavo-meilusgustavo-meilus/superpipelines/CLAUDE.md

superpipelines

CLAUDE.md4 starsChanged 6 months agoMITView on GitHub

Project Version: v2.5.0 CLAUDE.md is a wrapper. Keep durable cross-agent context in AGENTS.md; keep Claude-only workflow notes here. Before architecture, skill, agent, manifest, model-routing, or dispatch edits, treat AGENTS.md, docs/adr/, and the relevant skills/*/SKILL.md as required context. For this repo, Claude Code plugin agents are intentionally frontmatter-only. Structural barriers for plugin-shipped agents come from tools: and disallowedTools:; do not rely on plugin-scope permissionMode as the enforcement mechanism. Use .aiboarding/tools/check-size-budget AGENTS.md after onboarding edits. On Windows without Git Bash, aiboarding hooks…

The file

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

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

  • 2

    Very specific

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

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

    Before architecture, skill, agent, manifest, model-routing, or dispatch edits, treat AGENTS.md, docs/adr/, and the relevant …

    line 10
  2. Very specific:

    Use .aiboarding/tools/check-size-budget AGENTS.md after onboarding edits.

    line 14

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

@AGENTS.md

<!-- aiboarding-begin:claude-notes -->

Claude Code Notes

Project Version: v2.5.0

CLAUDE.md is a wrapper. Keep durable cross-agent context in AGENTS.md; keep Claude-only workflow notes here.

Before architecture, skill, agent, manifest, model-routing, or dispatch edits, treat AGENTS.md, docs/adr/, and the relevant skills/*/SKILL.md as required context.

For this repo, Claude Code plugin agents are intentionally frontmatter-only. Structural barriers for plugin-shipped agents come from tools: and disallowedTools:; do not rely on plugin-scope permissionMode as the enforcement mechanism.

Use .aiboarding/tools/check-size-budget AGENTS.md after onboarding edits. On Windows without Git Bash, aiboarding hooks may not execute, but native @AGENTS.md loading still works.

<!-- aiboarding-end:claude-notes -->

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.