agentleFS
MagicJoshMagicJosh/ras/skills/rules/SKILL.md

rules

Skill1 starsChanged 9 days agoMITView on GitHub

Use when the user types /rules to install the lazy senior dev coding rules for every session. Copies them to ~/.claude/rules/lazy.md and never overwrites without asking.

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    review

    Fixture review skill.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Read references/lazy.md from this skill.

    line 13
  2. Very specific:

    If ~/.claude/rules/lazy.md does not exist, write the file with that exact text.

    line 14
  3. Distinctive:

    If the file exists and differs, show the difference.

    line 15

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “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
SKILL.md

Rules

Install the lazy senior dev rules as a user rule file. Claude Code loads every file in ~/.claude/rules/ at the start of each session, in every project.

Steps

  1. Read references/lazy.md from this skill.
  2. If ~/.claude/rules/lazy.md does not exist, write the file with that exact text. Create the folder if needed.
  3. If the file exists and differs, show the difference. Replace it only if the user says yes.
  4. If ~/AGENTS.md, ~/CLAUDE.md or another file in ~/.claude/rules/ holds similar rules, tell the user. Claude Code reads an AGENTS.md only when no CLAUDE.md is in the working directory or above it, so the rule file is the reliable place. Two copies load the rules twice. Offer to remove the old copy, and do not remove it yourself.
  5. Tell the user that the rules load from the next session.

Rules

  • Change nothing else in ~/.claude/.

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.