agentleFS
Sign inStart free
loursCreatifloursCreatif/ours-stack/CLAUDE.md

ours-stack

CLAUDE.md1 starsChanged 4 months agoMITView on GitHub

This file exists for runtimes that read CLAUDE.md. The portable source of truth is AGENTS.md plus each */SKILL.md.

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow the requested skill directly when the user invokes one.

    line 7
  2. Distinctive:

    Prefer the capability exposed by the current runtime over a named agent or provider.

    line 8
  3. Distinctive:

    Ask only when the missing answer changes the next action.

    line 9
  4. Distinctive:

    Keep edits scoped, preserve the artifact contract, and verify with the repo's available scripts/tests when relevant.

    line 10

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

ours-stack runtime notes

This file exists for runtimes that read CLAUDE.md. The portable source of truth is AGENTS.md plus each */SKILL.md.

Operating principles

  • Follow the requested skill directly when the user invokes one.
  • Prefer the capability exposed by the current runtime over a named agent or provider.
  • Ask only when the missing answer changes the next action; otherwise make a conservative assumption and proceed.
  • Keep edits scoped, preserve the artifact contract, and verify with the repo's available scripts/tests when relevant.
  • For large work, use any available sub-agent, task, or browser capability when it improves quality, but never require a specific product.

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.

Check your setup, free