agentleFS
Sign inStart free
zajcazajca/pohunek/CLAUDE.md

pohunek

CLAUDE.md8 starsChanged 9 days agoMITView on GitHub

Read AGENTS.md first. It routes tasks to Pohunek's canonical, scoped instructions; do not maintain a second copy of repository policy here. - For product boundaries and compatibility, follow .agents/instructions/project.md and docs/architecture.md. - For code, tests, and verification, follow .agents/instructions/coding.md and .agents/instructions/verification.md. - Before any Rust edit, follow .agents/rust-guidelines/SKILL.md. - For issue and project writes, follow the github-workflow skill. - Use the relevant milestone, review, gate, handoff, or release skill under .agents/skills/ when its workflow applies. .claude/skills/ points to those canonical…

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
  1. Very specific:

    Read AGENTS.md first. It routes tasks to Pohunek's canonical, scoped instructions.

    line 3
  2. Very specific:

    Before any Rust edit, follow .agents/rust-guidelines/SKILL.md.

    line 12
  3. Very specific:

    Use the relevant milestone, review, gate, handoff, or release skill under .agents/skills/ when its workflow applies.

    line 16

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

Claude Code

Read AGENTS.md first. It routes tasks to Pohunek's canonical, scoped instructions; do not maintain a second copy of repository policy here.

  • For product boundaries and compatibility, follow .agents/instructions/project.md and docs/architecture.md.
  • For code, tests, and verification, follow .agents/instructions/coding.md and .agents/instructions/verification.md.
  • Before any Rust edit, follow .agents/rust-guidelines/SKILL.md.
  • For issue and project writes, follow the github-workflow skill.
  • Use the relevant milestone, review, gate, handoff, or release skill under .agents/skills/ when its workflow applies. .claude/skills/ points to those canonical files; edit only .agents/skills/.

Host-level instructions may add constraints. They do not replace this repository's security, compatibility, testing, and authorization requirements, and the testing policy in .agents/instructions/verification.md takes precedence over a host rule that asks for tests for all new code.

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