agentleFS
Sign inStart free
CodeWithJuberCodeWithJuber/forgekit/CLAUDE.md

forgekit

CLAUDE.md2 starsChanged 4 months agoMITView on GitHub

- Zero runtime dependencies — CI enforces this. Everything uses Node.js built-ins. - ESM only — use import, never require. - Match existing patterns: dynamic await import() for optional modules, brand tokens from src/brand.js (never hardcode "Forge"/"forge"), BRAND.root for package root paths. - Run npm test && npx biome check && npm run typecheck && node src/cli.js docs check before committing — the docs check fails CI when commands/env vars/MCP tools/CHANGELOG drift from the code, so update docs IN THE…

The file

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:

    Test: npm test (node:test, 1000+ tests)

    line 12
  2. Very specific:

    After editing CHANGELOG.md (or commands/MCP tools), run node src/cli.js docs render: it regenerates the machine-owned blocks, including the …

    line 27

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

forgekit — contributor instructions

Stack

  • Node.js >=20, pure ESM ("type": "module"), zero runtime dependencies.
  • Linter/formatter: Biome 2.5.15 (dev dependency; npx biome migrate --write after an upgrade).
  • Types: TypeScript via JSDoc annotations — no .ts files, checked by tsc.

Commands

  • Install: npm ci
  • Test: npm test (node:test, 1000+ tests)
  • Lint + format: npm run check (the npx package is @biomejs/biome, not biome)
  • Typecheck: npm run typecheck
  • Build pages: npm run pages:build

Rules

  • Zero runtime dependencies — CI enforces this. Everything uses Node.js built-ins.
  • ESM only — use import, never require.
  • Match existing patterns: dynamic await import() for optional modules, brand tokens from src/brand.js (never hardcode "Forge"/"forge"), BRAND.root for package root paths.
  • Run npm test && npx biome check && npm run typecheck && node src/cli.js docs check before committing — the docs check fails CI when commands/env vars/MCP tools/CHANGELOG drift from the code, so update docs IN THE SAME CHANGE, not later.
  • After editing CHANGELOG.md (or commands/MCP tools), run node src/cli.js docs render: it regenerates the machine-owned blocks, including the Mintlify changelog page (mintlify/changelog/overview.mdx), which the docs check fails on when stale. Never edit between forge:render markers by hand.
  • Version lives in package.json — scripts/bump.mjs keeps all manifests in sync.

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