agentleFS
Sign inStart free
yuzutechyuzutech/kroki/CLAUDE.md

kroki

CLAUDE.md4.4k starsChanged 40 days agoMITView on GitHub

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

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

  • 2

    Very specific

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

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

    Update CHANGELOG.md whenever you make a user-facing change: add an entry under ## [Unreleased], in the appropriate Keep a Changelog …

    line 3
  2. Very specific:

    Run the linter (npm run lint in mermaid/, i.e.

    line 5

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 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

Project conventions

  • Update CHANGELOG.md whenever you make a user-facing change: add an entry under ## [Unreleased], in the appropriate Keep a Changelog category (Added/Changed/Fixed/Security/Diagram libraries/...), following the existing entry style (short description + PR link).
  • Internal-only dependency bumps (build tooling, test libraries, CI actions, low-level Java libs like netty/vertx/opentelemetry) are not changelog-worthy on their own — only note dependency updates that are user-visible (diagram library versions, base Docker image versions) or security-relevant.
  • Run the linter (npm run lint in mermaid/, i.e. biome check src) whenever you make changes under mermaid/.

Download now (ZIP)

Trending

Less talk lately.about the whole repository

Dec 2025: 8 mentionsJan 2026: 5 mentionsFeb 2026: 3 mentionsMar 2026: 5 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 7 mentionsJul 2026: 1 mentionAug 2026: 1 mentionSep 2026: 1 mentionOct 2026: 2 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the yuzutech/kroki repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about yuzutech/kroki

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

See all 50

Talked about on GitHub (50 times).

On GitHub · 50

45 more on GitHub

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