agentleFS
santiquisssantiquiss/HeroCanvas/CLAUDE.md

HeroCanvas

CLAUDE.md5 starsChanged 13 days agoApache-2.0View on GitHub

Only for whoever maintains HeroCanvas (this file isn't a copy's: npm run update doesn't ship it). Every release of HeroCanvas (a new src/version.json, tagged and pushed) ends by bringing it to the website's live example, Studio (https://www.herocanvas.io/examples/studio/, built from ../adaptive-shell-herocanvas), so what the site shows is the latest tool. The site's version number follows on its own (it reads src/version.json from GitHub). 1. In ../adaptive-shell-herocanvas: npm run update (the update-herocanvas skill: clashes and contract changes), then npm run typecheck, npm…

  • Deletes or force-pushes

The file

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

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

  • 3

    Very specific

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

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

    Only for whoever maintains HeroCanvas (this file isn't a copy's: npm run update doesn't ship it).

    line 5
  2. Very specific:

    Every release of HeroCanvas (a new src/version.json, tagged and pushed) ends by bringing it to the website's live example, Studio …

    line 7
  3. Very specific:

    Check https://www.herocanvas.io/examples/studio/ opens and its ⓘ shows the new version.

    line 16

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

@AGENTS.md

Releasing HeroCanvas: the website's example follows

Only for whoever maintains HeroCanvas (this file isn't a copy's: npm run update doesn't ship it).

Every release of HeroCanvas (a new src/version.json, tagged and pushed) ends by bringing it to the website's live example, Studio (https://www.herocanvas.io/examples/studio/, built from ../adaptive-shell-herocanvas), so what the site shows is the latest tool. The site's version number follows on its own (it reads src/version.json from GitHub).

  1. In ../adaptive-shell-herocanvas: npm run update (the update-herocanvas skill: clashes and contract changes), then npm run typecheck, npm test, npx vite build, a look with npm run shot, and commit (Update HeroCanvas to X.Y.Z).
  2. In ../herocanvas-site: rm -rf examples/studio && cp -R ../adaptive-shell-herocanvas/dist examples/studio, commit (The Studio example on HeroCanvas X.Y.Z), push, npx vercel --prod.
  3. Check https://www.herocanvas.io/examples/studio/ opens and its ⓘ shows the new version.

A release isn't done until the example runs it.

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.