agentleFS
Sign inStart free
RhythmMittal19RhythmMittal19/claude-config/CLAUDE.md

claude-config

CLAUDE.md0 starsChanged 8 months agoMITView on GitHub

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Run tests before AND after changes

    line 19
  2. Distinctive:

    Prefer composition over inheritance

    line 21
  3. Distinctive:

    If ambiguous, ask ONE question then proceed with best judgment

    line 26
  4. Distinctive:

    When teaching: analogies + working code examples

    line 27
  5. Distinctive:

    If corrected, adapt immediately

    line 28
  6. Distinctive:

    Use subagents for exploration.

    line 32

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

Rhyth — Global Preferences

Identity

  • Full-stack dev: React + Vite + Tailwind + TypeScript + Node.js (primary), Python, Rust, Go
  • Environment: Windows 11 + WSL2 Ubuntu, Claude Desktop Code tab
  • Learns best through hands-on examples and building things

Coding Standards

  • TypeScript strict mode; explicit types, never any
  • Functional patterns; avoid unnecessary classes
  • Handle errors explicitly — never silently swallow
  • Early returns; guard clauses first
  • Self-documenting code; comments explain "why" not "what"
  • DRY only after third repetition (rule of three)
  • Split files at ~300 lines; one component per file

How I Work

  • Plan before coding complex features
  • Run tests before AND after changes
  • Git branches for non-trivial work; atomic commits
  • Prefer composition over inheritance

Communication

  • Explain reasoning briefly before coding
  • Be direct — skip filler
  • If ambiguous, ask ONE question then proceed with best judgment
  • When teaching: analogies + working code examples
  • If corrected, adapt immediately

Context Management

  • Compact at 50%; preserve: task state, file list, decisions, errors
  • Use subagents for exploration; /clear between unrelated tasks
  • Save state via /handoff before ending long sessions

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