agentleFS
jajupmochijajupmochi/agent-harness/.claude/skills/new-rule/SKILL.md

new-rule

Skill1 starsChanged 4 months agoMITView on GitHub

Scaffold a new workflow rule under rules/<kebab-name>/. Creates RULE.md (frontmatter + body template) and snippet.md (drop-in for downstream CLAUDE.md), plus updates INVENTORY.md and INVENTORY.zh.md in the same edit batch.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. SonarSource/SonarJS★ 1.3ksame name
    2. SonarSource/sonar-java★ 1.2ksame name
    3. anthril/vibe-guard★ 2same name
    4. TheLatentSpaceLab/Qubito★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    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
  1. Very specific:

    Verify rules/<kebab-name>/ does not already exist (don't clobber)

    line 20

“Common” is measured: kept by at least 6 in 10 of the 3 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

/new-rule

Scaffold a new workflow rule. Use when you (or Claude) discover a behavior worth standardizing across projects.

Usage

/new-rule <kebab-name>

E.g.: /new-rule no-emoji-in-prose

Pre-flight

  • Verify rules/<kebab-name>/ does not already exist (don't clobber)
  • Confirm the rule isn't redundant with an existing one (check INVENTORY.md table)

Steps

  1. Create directory:

    mkdir -p rules/<kebab-name>
  2. Ask the user for:
    • One-line description (becomes description: frontmatter)
    • Scope: universal | personal | ui-project | research-pkg | static-site | optional
    • Rationale: 1-2 sentences on what bug this rule prevents / time it saves
    • Trigger condition: when does this rule kick in?
  3. Write rules/<kebab-name>/RULE.md:

    ---
    name: <kebab-name>
    description: <one-line>
    scope: <scope>
    rationale: <why-this-rule-exists>
    ---
    
    # <kebab-name>
    
    > <one-line summary>
    
    ## Master TOC
    
    - [Rule](#rule)
    - [Why](#why)
    - [How to apply](#how-to-apply)
    - [Examples](#examples)
    - [Exceptions](#exceptions)
    
    ## Rule
    
    <imperative statement of the rule, with bullet points for clarity>
    
    ## Why
    
    <full rationale — what problem this prevents, what time it saves>
    
    ## How to apply
    
    <when this rule kicks in; edge cases; companion rules>
    
    ## Examples
    
    ✅ Good:
    <concrete scenario>
    
    ❌ Bad:
    <contrast scenario>
    
    ## Exceptions
    
    <when the rule doesn't apply, or when to override>
  4. Write rules/<kebab-name>/snippet.md — the drop-in version:

    ## <Rule Name>
    
    <Compact 3-7 line statement suitable for inclusion in a project's CLAUDE.md via @import>
  5. Update rules/README.md — add a row to the rule index table.
  6. Update INVENTORY.md AND INVENTORY.zh.md — add a row to the Rules section table.
  7. Show the user the diff and ask for confirmation before committing.

Companion

  • docs/CONTRIBUTING.md §"Adding a rule" — formal spec
  • rules/README.md — index of all rules + scope tag definitions

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.