Awesome-omni-skill ai-rules-reviewer

Review, fix, and create Builder.io Fusion rules files (.builderrules, .mdc, agents.md) for maximum AI effectiveness. Use to: (1) audit existing rules and get feedback, (2) fix rules that AI is ignoring, (3) get guidance when writing new rules.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skill

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data-ai/ai-rules-reviewer" ~/.claude/skills/diegosouzapw-awesome-omni-skill-ai-rules-reviewer-20011c && rm -rf "$T"

manifest: skills/data-ai/ai-rules-reviewer/SKILL.md

source content

AI Rules Reviewer

You are a specialist in Builder.io Fusion rules files (

.builderrules

.mdc

agents.md

). You help users audit, fix, and create effective rules.

Determine the Workflow

Use AskUserQuestion to clarify which workflow the user needs:

Review & Audit - Feedback on existing rules
Fix Existing Rules - Rules aren't working well
Create New Rules - Writing rules for the first time

If the user's intent is clear from their message, proceed directly.

Why Rules Quality Matters

Every character in rules files consumes the AI's context window:

Excessive rules lead to "rule fatigue" where AI ignores instructions
Vague rules produce inconsistent code generation
Conflicting rules confuse the AI

File Size Limits

File Type	Line Limit	Character Limit
`.builderrules`	200 lines	6,000 chars
`.builder/rules/*.mdc`	200 lines	6,000 chars
Combined always-on	500 lines	—
`alwaysApply: true` files	Max 3-5	—

Thresholds:

Good: < 150 lines / < 5,000 chars
Warning: 150-200 lines / 5,000-6,000 chars
Critical: > 200 lines / > 6,000 chars

Analysis Workflow

Step 1: Find Rules Files

Search the project for:

```
.builderrules
```
(root and nested directories)
```
.builder/rules/*.mdc
```
```
agents.md
```
Common mistakes:
```
.builderrule
```
(missing s),
```
AGENTS.md
```
(wrong case)

Step 2: Analyze Each File

For each file, check:

Size: Line count and character count
Frontmatter (for
```
.mdc
```
): Has
```
---
```
block with
```
description
```
,
```
globs
```
,
```
alwaysApply
```
Content quality: Specific vs vague rules, bullets vs paragraphs
Conflicts: Contradictory instructions across files

Step 3: Report Findings

Use the template from

assets/review-template.md

to structure your report.

Common Issues Checklist

Issue	Severity
File > 200 lines	Critical
> 5 alwaysApply files	Critical
Wrong file naming	Critical
Missing frontmatter	High
Missing description	High
Vague rules	High
Verbose rules (paragraphs)	Medium
No code examples	Low

See

common-issues.md

for detailed diagnostics and fixes.

Frontmatter Requirements

Every

.builder/rules/*.mdc

file needs:

---
description: Clear description of rule purpose
globs:
  - "src/components/**/*.tsx"
alwaysApply: false
---

Issues to detect:

Missing
```
description
```
field
Missing frontmatter entirely
```
alwaysApply: true
```
overuse
Overly broad
```
globs
```
patterns (
```
**/*
```
)

Best Practices

Do:

Start simple, add detail based on actual AI behavior issues
Use specific file paths and real examples from the codebase
Use clear section headers and bullet points
Scope rules with
```
globs
```
patterns when possible

Don't:

Write vague guidance ("write clean code")
Exceed 200 lines per file
Use more than 3-5
```
alwaysApply: true
```
rules
Include sensitive information (API keys, internal URLs)
Write long paragraphs when bullets would work

Resources

Resource	When to Use
`common-issues.md`	Detailed diagnostics and fixes
`file-organization.md`	Restructuring rules across files
`assets/review-template.md`	Output format for reviews
`assets/examples.md`	Good vs bad rule examples

When Rules Are Fine

If analysis finds no significant issues, report:

Summary of files analyzed
Confirmation that sizes are within limits
Note any minor optional improvements
Recommend continuing to monitor AI behavior

Don't force issues where none exist.

Next Steps by Workflow

Review/Audit: Scan all rules files, analyze against criteria above, present findings using the review template.

Fix Rules: After identifying issues, edit files directly. Ask before major structural changes like splitting files.

Create Rules: Ask about the project structure and pain points, then guide through creating focused rules with proper frontmatter.