agentleFS
KalastajaMKalastajaM/Cluide/CLAUDE.md

Cluide

CLAUDE.md2 starsChanged 3 months agoMITView on GitHub

The imported AGENTS.md is the canonical shared repository policy. If this interface does not resolve imports, explicitly read the root AGENTS.md before working. Do not duplicate shared rules here. Claude routing exceptions for work delegated from sessions in this repository — subagents, workflow stages, scheduled tasks. The dispatch skill (skills/dispatch/SKILL.md) applies wherever this section is silent. For conversational Claude setup, see PLATFORM_SETUP.md.

The file

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

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

  • 1

    Very specific

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

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

    Default worker tier: sonnet, replacing the table's haiku rows — only the known-safe list below runs on haiku.

    line 14
  2. Distinctive:

    Never below opus for: writing or reviewing guide prose that ships, and review verdicts on guides, skills or templates — publication quality …

    line 15

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

Cluide — Claude Entry Point

@AGENTS.md

The imported AGENTS.md is the canonical shared repository policy. If this interface does not resolve imports, explicitly read the root AGENTS.md before working. Do not duplicate shared rules here.

Claude-only

Dispatch Overrides

Claude routing exceptions for work delegated from sessions in this repository — subagents, workflow stages, scheduled tasks. The dispatch skill (skills/dispatch/SKILL.md) applies wherever this section is silent.

  • Before executing any task with bulk, parallel or mechanical parts, load the dispatch skill — even when another skill (a maintenance playbook, a review protocol) has already supplied the procedure. Playbooks say what to do; dispatch says which tier does it. Under the inline floor, doing it inline is correct; log it as inline.
  • Default worker tier: sonnet, replacing the table's haiku rows — only the known-safe list below runs on haiku. Pass model on every spawn of an unpinned agent type; an omitted one inherits the session's tier.
  • Never below opus for: writing or reviewing guide prose that ships, and review verdicts on guides, skills or templates — publication quality is this repository's whole product.
  • Known-safe on haiku: link checks, byte-identity mirror sweeps (diff -q), guide-number citation greps, file inventories — anything the merge gate defines mechanically.
  • The default tier and the known-safe list are cost rules: raise the tier when a task is harder than its archetype. The never-below line is a tier floor and is not traded against cost.
  • Log dispatches to development/ROUTING_LOG.md (gitignored working state: this section is the published example, the log is not).

For conversational Claude setup, see PLATFORM_SETUP.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.