Create moyu.mdc with anti-over-engineering rules

[uucz]

Added guidelines to prevent over-engineering in AI responses.

Summary by CodeRabbit

• Chores
  • Added a new development rule file to enhance code quality standards and development practices.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new markdown rule file rules-new/moyu.mdc is introduced with frontmatter metadata and instructions designed to constrain AI-assisted code changes to requested modifications only, emphasizing simplicity and prohibiting unnecessary additions like abstractions, comments, dependencies, or file rewrites.

Changes

Cohort / File(s)	Summary
New Rule File rules-new/moyu.mdc	Added markdown rule file with metadata and instructions to enforce minimal, focused code changes and prevent over-engineering in AI-generated modifications.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A humble file hops into place,
With rules to keep ambition in check.
"Just what was asked," it gently states,
No extra fluff, no needless trek.
Simplicity reigns, the rabbit's way! 🐰

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Create moyu.mdc with anti-over-engineering rules' clearly and specifically describes the main change—adding a new markdown rule file with anti-over-engineering guidelines.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

rules-new/moyu.mdc (1)

2-2: Avoid unverifiable performance claims in rule metadata.

At Line 2, the “47% across 8 models” statement is a strong claim without traceable evidence here. Prefer neutral wording or link a source to avoid stale/misleading policy text.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@rules-new/moyu.mdc` at line 2, Update the description metadata string to
remove or neutralize the unverifiable performance claim found in the description
line (the text "47% across 8 models"); either delete that numeric claim or
replace it with non-quantitative wording (e.g., "significantly reduces code
output across models") or add a verifiable citation reference; ensure you update
the same description field so the rule text remains accurate and
evidence-backed.

🤖 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-new/moyu.mdc`:
- Line 2: Update the description metadata string to remove or neutralize the
unverifiable performance claim found in the description line (the text "47%
across 8 models"); either delete that numeric claim or replace it with
non-quantitative wording (e.g., "significantly reduces code output across
models") or add a verifiable citation reference; ensure you update the same
description field so the rule text remains accurate and evidence-backed.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d8bf68a8-7922-4138-b673-a99c6318467d

📥 Commits

Reviewing files that changed from the base of the PR and between fc2ce04 and ee54033.

📒 Files selected for processing (1)

• rules-new/moyu.mdc