agentleFS
cheaper-inferencecheaper-inference/OmniRoute/CLAUDE.md

OmniRoute

CLAUDE.md83k starsChanged 10 days agoMITView on GitHub

All project rules live in AGENTS.md — the single source of truth for every AI assistant (architecture, conventions, testing, quality gates, git workflow, the 23 Hard Rules, PII learnings). Read it in full; do not re-add project rules here. Everything below applies ONLY to Claude Code — operational refinements of rules already defined in AGENTS.md. The full mandatory worktree protocol (base-branch confirmation, .claude/worktrees/ canonical path, cp -al nodemodules, teardown rules) is in docs/ops/WORKTREEISOLATION.md (summarized in AGENTS.md → Git Workflow →…

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

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

  • 5

    Very specific

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

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

    Prefer the native EnterWorktree tool — it already creates worktrees under .claude/worktrees/ (the canonical path).

    line 19
  2. Very specific:

    Before merging or pushing to any PR you did not create _this session_, run git worktree list and re-check gh pr view <N> --json …

    line 31
  3. Very specific:

    Commit those artifacts inside the _tasks/ repo (git -C _tasks …), never in the main repo.

    line 49
  4. Very specific:

    Do not confuse this with _tasks/ (Hard Rule #23, its own private git repo for durable plans/specs/research/hand-offs) — _artifacts/ is for …

    line 62
  5. Very specific:

    Before cutting a branch or opening a PR, run the base-green check (AGENTS.md → Git Workflow → "Base-green check".

    line 68

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

@AGENTS.md

All project rules live in AGENTS.md — the single source of truth for every AI assistant (architecture, conventions, testing, quality gates, git workflow, the 23 Hard Rules, PII learnings). Read it in full; do not re-add project rules here. Everything below applies ONLY to Claude Code — operational refinements of rules already defined in AGENTS.md.

Worktree isolation — Claude Code specifics

The full mandatory worktree protocol (base-branch confirmation, .claude/worktrees/ canonical path, cp -al node_modules, teardown rules) is in docs/ops/WORKTREE_ISOLATION.md (summarized in AGENTS.md → Git Workflow → "Worktree isolation"). Claude-Code-specific points:

  • Confirm the base branch with the operator via AskUserQuestion (Hard Rule #19) unless they already told you.
  • Prefer the native EnterWorktree tool — it already creates worktrees under .claude/worktrees/ (the canonical path). Create the worktree with the documented git worktree add command, then call EnterWorktree with its path.

Cross-session safety — Claude Code specifics

Hard Rules #19/#21/#22 (in AGENTS.md) govern parallel sessions. Operational reminders for this harness:

  • Replicate the git stash ban verbatim in the prompt of every subagent that touches git (Agent tool / Workflow scripts) — subagents do not inherit this file, and the recorded recurrence of the stash incident came through a subagent.
  • Before merging or pushing to any PR you did not create this session, run git worktree list and re-check gh pr view <N> --json state,headRefOid (Hard Rule #22b).
  • End every session with the main checkout on the branch it started on.

Superpowers / planning artifacts — path overrides

The _tasks/ convention is defined in AGENTS.md → "Planning & Research Artifacts". The superpowers skills ship with defaults that point at docs/… — those defaults are overridden here. When a superpowers skill announces a path like "saved to docs/superpowers/plans/…", rewrite it to the _tasks/… equivalent before writing:

Artifact (skill)Default (do NOT use)Save here instead
Plans (writing-plans)docs/superpowers/plans/_tasks/superpowers/plans/YYYY-MM-DD-<feature>.md
Specs / design (brainstorming)docs/superpowers/specs/_tasks/superpowers/specs/YYYY-MM-DD-<topic>-design.md
Research (deep-research, ad-hoc)docs/research/_tasks/research/…
Hand-offs (/handoff)—_tasks/hands-off/<YYYY-MM-DD>_<branch>_v<versão>_sess-<id>/

Commit those artifacts inside the _tasks/ repo (git -C _tasks …), never in the main repo.

Scratch / temporary files — use _artifacts/, not /tmp

This project overrides the harness's default session scratchpad (/tmp/claude-*/…). Write temporary/working files — exports, generated zips, one-off intermediate outputs, anything you'd otherwise put in /tmp — to /home/diegosouzapw/dev/proxys/OmniRoute/_artifacts/ instead.

  • _artifacts/ is a root _* path: already gitignored (AGENTS.md → "Root _* paths"), lives on disk only, never tracked.
  • Reason: keeping scratch output inside the project (vs /tmp) makes it trivial for the operator to find and delete everything temporary in one place, instead of hunting across ephemeral session-specific /tmp directories that vanish or accumulate untracked.
  • Do not confuse this with _tasks/ (Hard Rule #23, its own private git repo for durable plans/specs/research/hand-offs) — _artifacts/ is for disposable working files only, nothing here needs to survive or be versioned.

Base-green before opening PRs

Before cutting a branch or opening a PR, run the base-green check (AGENTS.md → Git Workflow → "Base-green check"; project skills reference it as .agents/skills/_shared/base-green.md). A PR opened while the base tip is red must carry ⚠️ base-red inherited: #<issue> in its body. To drain an accumulated red state (base tip + red PRs), use the /sweep-reds skill.

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about cheaper-inference/OmniRoute

The biggest 5 of 35 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 35

Talked about on YouTube, GitHub and the web (35 times).

On YouTube · 13

8 more on YouTube

On GitHub · 11

6 more on GitHub

On the web · 11

6 more on the web

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.