agentleFS
Sign inStart free
nonloopednonlooped/roblox-suite/CLAUDE.md

roblox-suite

CLAUDE.md25 starsChanged 56 days agoMITView on GitHub

Any change to the source or skills needs a version bump. Source and skills cover roblox*/ skills, references, and scripts; catalog.json, types/, schemas/, tests/, and site/ source. CI workflows and repo-level docs such as README and CONTRIBUTING do not need a bump unless they change published guidance. For each bump: A version bump is not finished until gh release view vX.Y.Z shows the release. Do not release a version without its CHANGELOG section, and do not leave a CHANGELOG section…

  • Commits and pushes

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:

    Add a ## X.Y.Z — YYYY-MM-DD section at the top of CHANGELOG.md.

    line 9
  2. Very specific:

    Commit the bump with the changes it releases and push it to origin/main.

    line 11

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

Agent rules

Version bumps and GitHub releases

Any change to the source or skills needs a version bump. Source and skills cover roblox*/ skills, references, and scripts; catalog.json, types/, schemas/, tests/, and site/ source. CI workflows and repo-level docs such as README and CONTRIBUTING do not need a bump unless they change published guidance.

For each bump:

  1. Add a ## X.Y.Z — YYYY-MM-DD section at the top of CHANGELOG.md.
  2. Set "version" to X.Y.Z in site/package.json and in both root "version" fields of site/package-lock.json.
  3. Commit the bump with the changes it releases and push it to origin/main.

  4. Publish a GitHub release for the bump commit, with the tag vX.Y.Z and the same name. Use the version's CHANGELOG section as the release notes, without the ## X.Y.Z heading:

    gh release create vX.Y.Z --target <bump-commit-sha> --title vX.Y.Z --notes-file <notes-file>

A version bump is not finished until gh release view vX.Y.Z shows the release. Do not release a version without its CHANGELOG section, and do not leave a CHANGELOG section without its release.

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