agentleFS
CyranoBCyranoB/web-forager/CLAUDE.md

web-forager

CLAUDE.md10 starsChanged 56 days agoMITView on GitHub

- Keep progress updates brief and report only material findings or changes in direction. - Complete the requested scope without silently expanding it; ask only when materially different interpretations would produce different work. - Delegate only substantial, independent work that benefits from parallel execution. Perform routine implementation and validation directly. - Lead the final response with the outcome, followed by essential evidence, caveats, and next steps. Track issues and specs in the public CyranoB/web-forager GitHub repository. Before issue operations, read…

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 progress updates brief and report only material findings or changes in direction.

    line 5
  2. Very specific:

    Before issue operations, read docs/agents/issue-tracker.md.

    line 19
  3. Very specific:

    Use the five default triage roles.

    line 23
  4. Very specific:

    Use a single root context and root ADR directory.

    line 28

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

@AGENTS.md

Claude Code

  • Keep progress updates brief and report only material findings or changes in direction.
  • Complete the requested scope without silently expanding it; ask only when materially different interpretations would produce different work.
  • Delegate only substantial, independent work that benefits from parallel execution. Perform routine implementation and validation directly.
  • Lead the final response with the outcome, followed by essential evidence, caveats, and next steps.

Agent skills

Issue tracker

Track issues and specs in the public CyranoB/web-forager GitHub repository. Before issue operations, read docs/agents/issue-tracker.md.

Triage labels

Use the five default triage roles. Before assigning a triage status, read docs/agents/triage-labels.md.

Domain docs

Use a single root context and root ADR directory. Before exploring the codebase, read docs/agents/domain.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.