agentleFS
AWSKnown publisherawslabs/industrial-shopfloor-connect/CLAUDE.md

industrial-shopfloor-connect

CLAUDE.md6 starsChanged 36 days agoApache-2.0View on GitHub

NEVER run any git command that changes repository state. Git is the user's business, not yours. Specifically, do NOT: - create, switch, rename, or delete branches (git branch, git checkout -b, git switch) - stage, commit, or amend (git add, git commit) - merge, rebase, cherry-pick, or reset (git merge, git rebase, git cherry-pick, git reset) - push, pull, or fetch (git push, git pull, git fetch) - stash, tag, or otherwise mutate refs or the working tree via git

  • Commits and pushes

The file

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

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    create, switch, rename, or delete branches (git branch, git checkout -b, git switch)

    line 8
  2. Distinctive:

    Read-only inspection is fine (git status, git log, git diff, git branch --show-current, git merge-base, git merge-tree dry-runs).

    line 14

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

Project rules

TOP PRIORITY — Git is off-limits

NEVER run any git command that changes repository state. Git is the user's business, not yours.

Specifically, do NOT:

  • create, switch, rename, or delete branches (git branch, git checkout -b, git switch)
  • stage, commit, or amend (git add, git commit)
  • merge, rebase, cherry-pick, or reset (git merge, git rebase, git cherry-pick, git reset)
  • push, pull, or fetch (git push, git pull, git fetch)
  • stash, tag, or otherwise mutate refs or the working tree via git

Read-only inspection is fine (git status, git log, git diff, git branch --show-current, git merge-base, git merge-tree dry-runs). If a task seems to need a state-changing git operation, STOP and ask the user to do it themselves.

AWS access is off-limits

NEVER use the AWS CLI or any AWS SDK to try to obtain account access. Do not run aws sts get-caller-identity, aws configure, aws login, aws sso login, or any CLI/SDK call whose purpose is to acquire, refresh, or probe credentials or account access. If a task seems to need AWS access, STOP and ask the user to perform the AWS step themselves.

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.