agentleFS
Sign inStart free
TJaenichenTJaenichen/claude-code-harness/CLAUDE.md

claude-code-harness

CLAUDE.md0 starsChanged 3 months agoMITView on GitHub

This is a public collection of Claude Code skills, agents, hooks and CLAUDE.md templates. Everything is generalized; see docs/placeholders.md for the legend. Rules when editing:

The file

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

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

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Never introduce real company, product, host, person or credential values.

    line 7
  2. Very specific:

    Run pwsh scripts/lint-placeholders.ps1 before committing.

    line 8
  3. Very specific:

    Prefer editing an existing skill over adding a near-duplicate.

    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

Working in this repo

This is a public collection of Claude Code skills, agents, hooks and CLAUDE.md templates. Everything is generalized; see docs/placeholders.md for the legend.

Rules when editing:

  • Never introduce real company, product, host, person or credential values. Use the placeholders from docs/placeholders.md (Contoso, Payments, devops.example.com, MainDb, 12345, Jane Doe).
  • Run pwsh scripts/lint-placeholders.ps1 before committing. It must print "No findings."
  • Skills stay in Claude Code's native layout: skills/<scope>/<name>/SKILL.md with frontmatter (name, description, argument-hint, allowed-tools). Helper scripts sit next to the SKILL.md that uses them.
  • Prefer editing an existing skill over adding a near-duplicate. If a skill is only meaningful with a tool that is not in this repo, leave it out and note it in docs/placeholders.md.
  • README prose: plain, direct, no em dashes.

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