agentleFS
instructkrinstructkr/claw-code/CLAUDE.md

claw-code

CLAUDE.md195k starsChanged 7 months agoMITView on GitHub

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Run Rust verification from repo root: scripts/fmt.sh --check.

    line 10
  2. Distinctive:

    Prefer small, reviewable changes and keep generated bootstrap files aligned with actual repo workflows.

    line 19
  3. Very specific:

    Keep shared defaults in .claude.json.

    line 20
  4. Distinctive:

    Do not overwrite existing CLAUDE.md content automatically.

    line 21

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

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Detected stack

  • Languages: Rust.
  • Frameworks: none detected from the supported starter markers.

Verification

  • Run Rust verification from repo root: scripts/fmt.sh --check; for formatting use scripts/fmt.sh. Run Rust clippy/tests from rust/: cargo clippy --workspace --all-targets -- -D warnings, cargo test --workspace
  • src/ and tests/ are both present; update both surfaces together when behavior changes.

Repository shape

  • rust/ contains the Rust workspace and active CLI/runtime implementation.
  • src/ contains source files that should stay consistent with generated guidance and tests.
  • tests/ contains validation surfaces that should be reviewed alongside code changes.

Working agreement

  • Prefer small, reviewable changes and keep generated bootstrap files aligned with actual repo workflows.
  • Keep shared defaults in .claude.json; reserve .claude/settings.local.json for machine-local overrides.
  • Do not overwrite existing CLAUDE.md content automatically; update it intentionally when repo workflows change.

Download now (ZIP)

Trending

Quiet since July.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 11 mentionsApr 2026: 45 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 1 mentionAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the instructkr/claw-code repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about instructkr/claw-code

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

See all 57

Talked about on Bluesky, GitHub, the web and Hacker News (57 times).

On Bluesky · 23

18 more on Bluesky

On GitHub · 18

13 more on GitHub

On the web · 13

8 more on the web

On Hacker News · 3

  • Other versions3 projects use a version of this.

    Word for word · 3

    1. ultraworkers/claw-code★ 195k100% same
    2. instructkr/claude-code★ 195k100% same
    3. instructkr/clawd-code★ 195k100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

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.