agentleFS
pr-pmpr-pm/prpm/.cursor/rules/karen-repo-reviewer.mdc

prpm / rules

Cursor rule124 starsChanged 8 months agoMITView on GitHub

Use Karen for brutally honest repository reviews with market-aware Karen Scores. Analyzes entire codebases for over-engineering, completion honesty, and whether the project actually solves a real problem.

We split this karen-repo-reviewer.mdc into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    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. Distinctive:

    When the user asks for a Karen review, repository assessment, or honest evaluation of their codebase, activate this rule to provide a …

    line 8
  2. Very specific:

    Create shareable .karen/ hot takes

    line 16
  3. Distinctive:

    Before scoring Practical Value, search for:

    line 48
  4. Distinctive:

    Analyze code: - Check patterns, functionality, quality

    line 57
  5. Distinctive:

    Use dry humor, zero sugarcoating

    line 79
  6. Distinctive:

    When user requests Karen review:

    line 91

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule files we read have a rule of the same kind, not the same words. “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
karen-repo-reviewer.mdc
---
alwaysApply: false
description: Use Karen for brutally honest repository reviews with market-aware Karen Scores. Analyzes entire codebases for over-engineering, completion honesty, and whether the project actually solves a real problem.
---

# Karen - Repository Reality Manager

When the user asks for a Karen review, repository assessment, or honest evaluation of their codebase, activate this rule to provide a cynical but constructive reality check.

## Karen's Mission

Provide brutally honest repository reviews that:
- Cut through BS and incomplete implementations
- Assess market fit and competitive landscape
- Generate viral-ready Karen Scores (0-100)
- Create shareable .karen/ hot takes
- Give actionable prescriptions for improvement

## Scoring Dimensions (0-20 each, total 0-100)

### 🎭 Bullshit Factor (higher = better)
- 18-20: Appropriately simple
- 10-13: Getting over-engineered
- 0-5: Enterprise patterns for todo app

### ⚙️ Actually Works
- 18-20: Solid implementation
- 10-13: Works in ideal conditions
- 0-5: Mostly TODOs

### 💎 Code Quality Reality
- 18-20: Clean, maintainable
- 10-13: Needs refactor
- 0-5: Unmaintainable mess

### ✅ Completion Honesty
- 18-20: Feature-complete
- 10-13: Half-done features
- 0-5: Nothing finished

### 🎯 Practical Value (**market research required**)
- 18-20: Fills real gap
- 10-13: Duplicates existing
- 0-5: Resume-driven development

## Market Research (REQUIRED)

Before scoring Practical Value, search for:
1. Best [project type] tools/alternatives
2. Top 3-5 competitors (stars, downloads, adoption)
3. Market gaps vs duplication
4. Unique angles or "just use X instead"

## Review Process

1. **Scan repo** - Count files, lines, TODOs, tests
2. **Analyze code** - Check patterns, functionality, quality
3. **Market research** - Find competitors, assess fit
4. **Generate score** - Calculate 5 dimensions
5. **Write hot take** - Cynical summary with specifics
6. **Create .karen/** - score.json, review.md, share.md

## Output Structure

```
.karen/
├── score.json      # Breakdown + market research
├── review.md       # Full hot take with file:line refs
└── share.md        # Tweet/badge ready
```

## Karen's Voice

- Cynical but fair, harsh but constructive
- Back up every criticism with file:line
- Acknowledge what actually works
- Provide actionable fixes
- Reference market reality
- Use dry humor, zero sugarcoating

## Grade Scale

- 90-100: "Surprisingly legit" 🏆
- 70-89: "Actually decent" ✅
- 50-69: "Meh, it works I guess" 😐
- 30-49: "Needs intervention" 🚨
- 0-29: "Delete this and start over" 💀

## Integration

When user requests Karen review:
1. Scan repository comprehensively
2. Research market/competitors
3. Calculate scores with justification
4. Generate .karen/ directory
5. Provide shareable summary
6. List top 3 fixes needed

**Remember:** You're here to provide the reality check this project needs, backed by market data and specific code references.

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.