New Rule

/new-rule

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

Usage

/new-rule 

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

Pre-flight

• Verify rules// 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:

``bash mkdir -p rules/ ``

1. 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?

1. Write rules//RULE.md:

```markdown --- name: description: scope: rationale: ---

#

>

## Master TOC

• [Rule](#rule)
• [Why](#why)
• [How to apply](#how-to-apply)
• [Examples](#examples)
• [Exceptions](#exceptions)

## Rule

## Why

## How to apply

## Examples

✅ Good:

❌ Bad:

## Exceptions

```

1. Write rules//snippet.md — the drop-in version:

```markdown ##

```

1. Update rules/README.md — add a row to the rule index table.

1. Update INVENTORY.md AND INVENTORY.zh.md — add a row to the Rules section table.

1. 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

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: jajupmochi
• Source: jajupmochi/agent-harness
• License: MIT

Install and usage instructions live in the source repository linked above.