Add Moyu anti-over-engineering cursor rules#211
Open
uucz wants to merge 1 commit intoPatrickJS:mainfrom
Open
Conversation
Adds Moyu (摸鱼), an anti-over-engineering ruleset that constrains AI from writing unnecessary code. Three iron rules: only change what was asked, simplest solution first, ask when unsure. Benchmarked at 66% code reduction. More info: https://github.com/uucz/moyu
Contributor
📝 WalkthroughWalkthroughA new rule configuration called "Moyu Anti-Over-Engineering" was added to the repository, comprising a prompt file defining guidelines for minimalist code changes and a corresponding README entry documenting its availability. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
🧹 Nitpick comments (2)
rules/moyu-anti-over-engineering-cursorrules-prompt-file/.cursorrules (2)
51-55: Define the "PUA" acronym for clarity.The section mentions "PUA" without explanation. Readers unfamiliar with this term won't understand the compatibility claim or what "PUA" is.
📝 Suggested clarification
## Works with PUA -PUA fixes laziness (AI does too little). Moyu fixes over-engineering (AI does too much). Install both for best results. +PUA (Pursue Until Acceptance) fixes laziness (AI does too little). Moyu fixes over-engineering (AI does too much). Install both for best results.Or provide a brief inline explanation or link to PUA documentation.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@rules/moyu-anti-over-engineering-cursorrules-prompt-file/.cursorrules` around lines 51 - 55, The term "PUA" in the section "## Works with PUA" is undefined; update the text around that heading to expand the acronym and/or add a brief parenthetical definition or a link to PUA documentation so readers know what PUA stands for and why it complements Moyu—e.g., change "PUA" to "PUA (Programmatic User Assistance)" or add "(see PUA docs)" after "PUA" in the same paragraph so the intent is clear.
1-55: Document the "66% code reduction" benchmark methodology.The PR summary and README claim "Benchmarked: 66% code reduction across 6 real coding tasks," but this file contains no documentation of the benchmark methodology, test cases, or measurement approach. For credibility and reproducibility, include:
- Which 6 coding tasks were used
- How code reduction was measured (lines? tokens? complexity?)
- Comparison baseline (AI without Moyu rules?)
- Links to benchmark data or results
Consider adding a "Benchmark Results" section to this file or creating a separate
BENCHMARK.mdin the same directory documenting the methodology and findings.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@rules/moyu-anti-over-engineering-cursorrules-prompt-file/.cursorrules` around lines 1 - 55, The PR claims "66% code reduction across 6 real coding tasks" but provides no methodology; add a reproducible Benchmark Results description either as a new BENCHMARK.md in the same directory or as a "Benchmark Results" section appended to .cursorrules that lists the six tasks (briefly name each task), specifies the measurement method (e.g., lines of code and token count and which tool/command computed tokens), the baseline used (exact model/config or "without Moyu rules" plus version), the aggregation method (how the 66% was computed), and links to raw data/results (CSV or gist) and commands to re-run the measurements; keep the wording short and factual and only touch .cursorrules or add BENCHMARK.md as the one file change.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@rules/moyu-anti-over-engineering-cursorrules-prompt-file/.cursorrules`:
- Around line 51-55: The term "PUA" in the section "## Works with PUA" is
undefined; update the text around that heading to expand the acronym and/or add
a brief parenthetical definition or a link to PUA documentation so readers know
what PUA stands for and why it complements Moyu—e.g., change "PUA" to "PUA
(Programmatic User Assistance)" or add "(see PUA docs)" after "PUA" in the same
paragraph so the intent is clear.
- Around line 1-55: The PR claims "66% code reduction across 6 real coding
tasks" but provides no methodology; add a reproducible Benchmark Results
description either as a new BENCHMARK.md in the same directory or as a
"Benchmark Results" section appended to .cursorrules that lists the six tasks
(briefly name each task), specifies the measurement method (e.g., lines of code
and token count and which tool/command computed tokens), the baseline used
(exact model/config or "without Moyu rules" plus version), the aggregation
method (how the 66% was computed), and links to raw data/results (CSV or gist)
and commands to re-run the measurements; keep the wording short and factual and
only touch .cursorrules or add BENCHMARK.md as the one file change.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: ba403ee8-40d5-4fc6-abf8-d9da4ca56563
📒 Files selected for processing (2)
README.mdrules/moyu-anti-over-engineering-cursorrules-prompt-file/.cursorrules
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New Rule: Moyu Anti-Over-Engineering
Repository: https://github.com/uucz/moyu
Adds Moyu (摸鱼) to the Other section — an anti-over-engineering ruleset for Cursor.
What it does: Constrains AI from writing unnecessary code through three iron rules:
Includes a grinding-vs-moyu comparison table, pre-delivery checklist, and anti-grinding impulse guide.
Benchmarked: 66% code reduction across 6 real coding tasks. Supports 10 AI coding platforms (Claude Code, Cursor, Codex, Copilot, Windsurf, Cline, Kiro, CodeBuddy, Antigravity, OpenCode).
Summary by CodeRabbit