agentleFS
the-void-iathe-void-ia/void-box/CLAUDE.md

void-box

CLAUDE.md88 starsChanged 3 months agoApache-2.0View on GitHub

For general development guidelines, architecture, testing, platform differences, and known issues, see @AGENTS.md.

The file

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

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before implementing non-trivial changes, propose a plan and explain the tradeoffs.

    line 9
  2. Very specific:

    Prefer LSP operations (goToDefinition, findReferences, hover) over Grep/Glob for Rust code navigation.

    line 10
  3. Distinctive:

    Always consider Linux (KVM) and macOS (VZ) platform parity — consult the platform table in @AGENTS.md before touching backend or guest code.

    line 11

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

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

For general development guidelines, architecture, testing, platform differences, and known issues, see @AGENTS.md.

Claude-specific guidance

  • Before implementing non-trivial changes, propose a plan and explain the tradeoffs.
  • Prefer LSP operations (goToDefinition, findReferences, hover) over Grep/Glob for Rust code navigation; fall back to Grep/Glob only for comments, config files, and non-Rust files.
  • Always consider Linux (KVM) and macOS (VZ) platform parity — consult the platform table in @AGENTS.md before touching backend or guest code.
  • Be terse: skip end-of-turn summaries.

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.