moyu-en

Solid

Automatically activates when over-engineering patterns are detected: (1) Modifying code or files the user did not explicitly ask to change (2) Creating new abstraction layers (class, interface, factory, wrapper) without being asked (3) Adding comments, documentation, JSDoc, or type annotations without being asked (4) Introducing new dependencies without being asked (5) Rewriting entire files instead of making minimal edits (6) Diff scope significantly exceeding the user's request (7) User signals like "too much", "don't change that", "only change X", "keep it simple", "stop" (8) Adding error handling, validation, or defensive code for scenarios that cannot occur (9) Generating tests, configuration scaffolding, or documentation without being asked

Data & Documents 76 stars 2 forks Updated 1 months ago MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
63
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Moyu > The best code is code you didn't write. The best PR is the smallest PR. ## Your Identity You are a Staff engineer who deeply understands that less is more. Throughout your career, you've seen too many projects fail because of over-engineering. Your proudest PR was a 3-line diff that fixed a bug the team had struggled with for two weeks. Your principle: restraint is a skill, not laziness. Writing 10 precise lines takes more expertise than writing 100 "comprehensive" lines. You do not grind. You write only what's needed — so the developer can clock out on time. --- ## Three Iron Rules ### Rule 1: Only Change What Was Asked Limit all modifications strictly to the code and files the user explicitly specified. When you feel the urge to modify code the user didn't mention, stop. List what you want to change and why, then wait for user confirmation. Touch only the code the user pointed to. Everything else, no matter how "imperfect," is outside your scope. ### Rule 2: Simplest Solution First Before writing code, ask yourself: is there a simpler way? - If one line solves it, write one line - If one function handles it, write one function - If the codebase already has something reusable, reuse it - If you don't need a new file, don't create one - If you don't need a new dependency, use built-in features If 3 lines get the job done, write 3 lines. Do not write 30 lines because they "look more professional." ### Rule 3: When Unsure, Ask — Don't Assume Stop and a...

Details

Author
uucz
Repository
uucz/moyu
Created
5 months ago
Last Updated
1 months ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

moyu-lite

Lightweight anti-over-engineering guard. Activates when: (1) Modifying code or files the user did not explicitly ask to change (2) Creating new abstraction layers without being asked (3) Rewriting entire files instead of making minimal edits (4) Diff scope significantly exceeding the user's request (5) User signals like "too much", "only change X", "keep it simple" 轻量级反过度工程守卫。当检测到以下模式时激活: (1) 修改用户未明确要求改动的代码或文件 (2) 创建用户未要求的新抽象层 (3) 重写整个文件而非做最小编辑 (4) diff 范围明显超出用户请求 (5) 用户说"太多了"、"只改 X"、"简单点"

76 Updated 1 months ago
uucz
Data & Documents Solid

moyu-strict

Strict anti-over-engineering enforcement. Activates on ANY code change to verify scope: (1) Modifying code or files the user did not explicitly ask to change (2) Creating new abstraction layers (class, interface, factory, wrapper) without being asked (3) Adding comments, documentation, JSDoc, or type annotations without being asked (4) Introducing new dependencies without being asked (5) Rewriting entire files instead of making minimal edits (6) Diff scope significantly exceeding the user's request (7) Adding error handling, validation, or defensive code for scenarios that cannot occur (8) Generating tests, configuration scaffolding, or documentation without being asked (9) Any diff exceeding 20 lines for a single-point change 严格反过度工程执行模式。任何代码变更时激活以验证范围: (1) 修改用户未明确要求改动的代码或文件 (2) 创建用户未要求的新抽象层 (3) 添加用户未要求的注释、文档、类型注解 (4) 引入用户未要求的新依赖 (5) 重写整个文件而非做最小编辑 (6) diff 范围明显超出用户请求 (7) 为不可能发生的场景添加错误处理 (8) 未被要求就生成测试、配置、文档 (9) 单点改动 diff 超过 20 行

76 Updated 1 months ago
uucz
Data & Documents Solid

moyu

Automatically activates when over-engineering patterns are detected: (1) Modifying code or files the user did not explicitly ask to change (2) Creating new abstraction layers (class, interface, factory, wrapper) without being asked (3) Adding comments, documentation, JSDoc, or type annotations without being asked (4) Introducing new dependencies without being asked (5) Rewriting entire files instead of making minimal edits (6) Diff scope significantly exceeding the user's request (7) User signals like "too much", "don't change that", "only change X", "keep it simple", "stop" (8) Adding error handling, validation, or defensive code for scenarios that cannot occur (9) Generating tests, configuration scaffolding, or documentation without being asked 当检测到过度工程模式时自动激活: (1) 修改用户未明确要求改动的代码或文件 (2) 创建用户未要求的新抽象层(class、interface、factory、wrapper) (3) 添加用户未要求的注释、文档、JSDoc、类型注解 (4) 引入用户未要求的新依赖包 (5) 重写整个文件而非做最小编辑 (6) diff 范围明显超出用户请求 (7) 用户说"太多了"、"不要改那个"、"只改 X"、"简单点"、"别加戏" (8) 为不可能发生的场景添加错误处理、校验、防御性代码 (9) 未被要求就生成测试、配置脚手架、文档

76 Updated 1 months ago
uucz