storytold
CLAUDE.md12 starsChanged 32 days agoMITView on GitHub
Read ../AGENTS.md for engineering constraints. The canonical runtime guidance is ../skills/craft/SKILL.md; generated plugins/storytold must not be edited by hand. Git workflow: main only, one commit per logical change. No feature branches or worktrees for repository changes, and upstream Craft links point at main, never at a release tag. No native process or permission grant is implied by opening this repository. Pull before anything else (git pull --ff-only origin main, or make github-pull when local commits are not pushed yet): the…
The file
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Very specific: line 3
Read ../AGENTS.md for engineering constraints.
- Distinctive: line 8
No native process or permission grant is implied by opening this repository.
≈ “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.
Files
Repository work
Read ../AGENTS.md for engineering constraints. The canonical runtime guidance is
../skills/craft/SKILL.md; generated plugins/storytold must not be edited by hand.
Git workflow: main only, one commit per logical change. No feature branches
or worktrees for repository changes, and upstream Craft links point at main,
never at a release tag.
No native process or permission grant is implied by opening this repository.
Pull before anything else (git pull --ff-only origin main, or make
github-pull when local commits are not pushed yet): the daily release workflow
merges its bot/releases pull request into main on its own. Commits go on main,
each one a single logical change that passes the gates alone and carries the
plugins/storytold it regenerates; push main, the v<version> tag and the GitHub
release happen only on the operator's explicit request in the current session.
Gates before a commit: make check, make test, make build and make verify-build;
a release adds make
release, make test-sdk and make host-validate. After a pin move, recheck the
moved apps' cards at their new tags as AGENTS.md describes.
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
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.