agentleFS
oryory/dockertest/CLAUDE.md

dockertest

CLAUDE.md4.5k starsChanged 13 months agoApache-2.0View on GitHub

- Always pass context.Context from caller (never use context.Background or TODO). - Follow idiomatic Go conventions (Effective Go). - Prefer simple, clean architectures versus overengineering. - Think about how you can remove, simplify, and reduce code (not tests!). LLMs and AI agents have a tendency to generate useless helpers that already exist in the stdlib or other libraries. Instead, I want you to delete and simplify code (do not delete test cases though) and not generate useless/duplicated/existing code. Generating useless…

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 1 mentionFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 1 mentionMay 2026: 1 mentionJun 2026: 1 mentionJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 2 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the ory/dockertest repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about ory/dockertest

The biggest 5 of 57 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 57

Talked about on GitHub, Stack Overflow, Bluesky and Hacker News (57 times).

On GitHub · 50

45 more on GitHub

On Stack Overflow · 4

The file

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

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

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Always pass context.Context from caller (never use context.Background or TODO).

    line 1
  2. Distinctive:

    Follow idiomatic Go conventions (Effective Go).

    line 3
  3. Distinctive:

    Prefer simple, clean architectures versus overengineering.

    line 5
  4. Distinctive:

    When tests fail, do not remove or disable them.

    line 16
  5. Distinctive:

    Do not use equality for error comparison.

    line 27
  6. Very specific:

    DO NOT use github.com/docker/docker but only github.com/moby/moby/client

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 27,641 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
  • Always pass context.Context from caller (never use context.Background or TODO).
  • Follow idiomatic Go conventions (Effective Go).
  • Prefer simple, clean architectures versus overengineering.
  • Think about how you can remove, simplify, and reduce code (not tests!). LLMs and AI agents have a tendency to generate useless helpers that already exist in the stdlib or other libraries. Instead, I want you to delete and simplify code (do not delete test cases though) and not generate useless/duplicated/existing code. Generating useless code or duplicating already existing functionality results in contract termination.
  • Implementation notes and plans and documents generated while developing belong in ./docs/notes/. Ensure that notes have a frontmatter with date, and reason fields. Specifically, the current date is important and the reason why the note was created.
  • When tests fail, do not remove or disable them. A failing test - especially if it already exists on the main branch - indicates a fault in the business logic. Removing or disabling that test leads to immediate contract termination.
  • Determinism is key, especially in tests and conformity checks. Avoid any sources of non-determinism such as random number generation, time-based functions, or reliance on external systems that may introduce variability. Non-deterministic behavior can lead to flaky tests and unpredictable application behavior, which is unacceptable. It is also unacceptable to have thresholds in tests (e.g. 99% match X) - tests must be deterministic and exact.
  • Do not use equality for error comparison. Always use errors.Is() or errors.As() for error comparisons.
  • In tests don't use defer for cleanup but t.Cleanup.
  • DO NOT use github.com/docker/docker but only github.com/moby/moby/client

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.