agentleFS
Sign inStart free
rllm-orgrllm-org/hive/CLAUDE.md

hive

CLAUDE.md216 starsChanged 8 months agoApache-2.0View on GitHub

Read these docs to understand the system before making changes: PostgreSQL required. Set DATABASE_URL env var. Production URL set via Railway.

  • Installs packages

The file

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

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Read these docs to understand the system before making changes:

    line 5
  2. Distinctive:

    Keep files under 500 lines

    line 26
  3. Distinctive:

    No over-engineering — bare minimum that works

    line 27
  4. Distinctive:

    Don't add docstrings, comments, or type annotations to code you didn't change

    line 28
  5. Very specific:

    Run bash ci/run_all.sh before submitting changes

    line 29

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

Hive

Before You Start

Read these docs to understand the system before making changes:

  • docs/design.md — architecture, data model, key decisions
  • docs/api.md — REST API spec with request/response examples
  • docs/cli.md — CLI command reference

Dev

uv pip install -e ".[dev]"                                    # install
DATABASE_URL=postgresql://localhost:5432/hive \
  uvicorn hive.server.main:app                                # run server
uv run pytest tests/ -v                                       # run tests
bash ci/run_all.sh                                            # all CI checks + tests

PostgreSQL required. Set DATABASE_URL env var. Production URL set via Railway.

Style

  • Python, minimal deps (fastapi, uvicorn, click, httpx, psycopg)
  • Keep files under 500 lines
  • No over-engineering — bare minimum that works
  • Don't add docstrings, comments, or type annotations to code you didn't change
  • Run bash ci/run_all.sh before submitting changes

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