Rule Catalog

**Run AI slop detection on documentation changes!**

When creating, updating, or rewriting documentation, run `Skill(scribe:slop-detector)` on all modified markdown files before considering the work complete.

**Common AI tells to watch for:**
- Em dash overuse (>1 per 1000 words is elevated, >5 is a strong
  AI signal; in prevention mode target zero)
- "structured", "actionable", "comprehensive", "seamless" and other tier 1 slop words
- Participial phrase tail-loading ("...enabling researchers to analyze data")
- Uniform sentence lengths (human writing varies, AI stays at 15-25 words)
- Hedging patterns ("It's important to note", "From a broader perspective")

**2026 prevention-strict tells (cross-source consensus):**
- Plus-sign for "and" in prose: "hooks + skills" → "hooks and skills"
- Spatial copula with inanimate subjects: "lives in", "sits
  at", "stands as", "rests on", "rooted in", "serves as",
  "boasts" → use "is" / "has" / "uses"
- Negative parallelism: "Not X but Y", "It's not X, it's Y",
  "No X. No Y. Just Z.", "And that's okay." → rewrite
  positively
- Throat-clearing openers: "Here's the thing,", "Look,",
  "Let that sink in.", "The uncomfortable truth is" → delete
- Three-fragment burst: "Focused. Aligned. Measurable." →
  single sentence
- Significance cluster: "stands as a testament to", "marks a
  turning point", "underscores the importance" → cut
- Smart quotes outside code blocks: `"text"` → `"text"`
- Loop/cascade vocabulary: "unpack" / "surface" (as verbs)
  in non-technical contexts

**Required workflow:**
1. Write/edit the documentation
2. Run `Skill(scribe:slop-detector)` on each modified .md file
3. Fix any issues with score > 2.0
4. Verify em dash count is within human range (0-2 per 1000 words)

**Quick checks:**
```bash
# Count em dashes in a file
grep -o '—' file.md | wc -l

# Count words
wc -w < file.md
```

**Why this rule exists:**
- AI-generated documentation erodes reader trust
- Em dashes, "structured", and "actionable" are the most common tells
- The slop detector exists but is only invoked manually today
- This rule closes the gap between writing docs and quality-checking them


---
name: block-destructive-git
enabled: true
event: bash
action: block
conditions:
  - field: command
    operator: regex_match
    pattern: git\s+(reset\s+--hard|checkout\s+--\s+\.|checkout\s+HEAD\s+--|checkout\s+\S+\s+--\s|restore\s+--source|clean\s+-[fd]+|stash\s+drop|branch\s+-D|reflog\s+expire|gc\s+--prune)
---

Uncommitted work represents someone's thinking.
Destroying it erases context that cannot be rebuilt.
(Care)

🛑 **Destructive Git Operation Blocked!**

This command can cause **irreversible data loss** - uncommitted changes, local branches, or reflog history may be permanently deleted.

## Detected Patterns

| Command | Risk | What It Destroys |
|---------|------|------------------|
| `git reset --hard` | 🔴 Critical | All uncommitted changes (staged and unstaged) |
| `git checkout -- .` | 🔴 Critical | All unstaged changes in working directory |
| `git checkout HEAD -- <file>` | 🟡 High | Specific file's uncommitted changes |
| `git checkout <branch> -- <path>` | 🔴 Critical | Overwrites files from another branch (undoes intentional changes) |
| `git restore --source` | 🟡 High | Overwrites files from another ref |
| `git clean -fd` | 🔴 Critical | All untracked files and directories |
| `git stash drop` | 🟡 High | Stashed changes permanently |
| `git branch -D` | 🟡 High | Force-deletes branch (even unmerged) |
| `git reflog expire` | 🔴 Critical | Recovery points for lost commits |
| `git gc --prune` | 🟡 High | Unreachable objects (can break recovery) |

## Recovery-First Approach

Before discarding changes, **always check w