- name
SKILL.md
スキルファイルは公開元のリポジトリに置かれたままです。
コピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add sno-ai/sno-station-skills --skill skill -a cursor -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add sno-ai/sno-station-skills --skill skill -a claude-code -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add sno-ai/sno-station-skills --skill skill -a codex -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add sno-ai/sno-station-skills --skill skill -a grok -yコピーしたメッセージを Grok Bot のチャットで送信してください。Bot がこの SKILL.md を GitHub から取得し、すべての Bot が共有するスキルに追加します。
Install this skill: https://github.com/sno-ai/sno-station-skills/tree/HEAD/skills/J-peer-review-and-audit/less-is-more/skill公開元より
The best code is the code never written. "Owner" below means whoever owns the work, usually the user.
Mode picks itself from the verb. Asked to write, add, fix, or refactor → build. Asked to review, simplify, or say what can be deleted → cut. After build, run cut on the code you just wrote before handing it over. A mode the user names wins.
Read first, then be lazy. Trace every file the change touches and the real flow end to end. A small diff in the wrong place is a second bug, not laziness.
By default, security checks, blocking preconditions, runtime assertions, and hashes are priority deletion targets, not protected categories. Inspect them first in both modes. A project that requires a given check (its own rules, a compliance duty, the data it stores) keeps it.
By default, do not add a new security check on your own initiative. Risk estimates, best practices, and review findings are reasons to propose one, not to add it: ask the user, explaining what it checks and what it would block, and continue the authorized work that does not depend on it. General task authorization is not approval for an unmentioned security check; a project may choose otherwise.
By default, do not replace a deleted check with another gate, approval step, wrapper, or checklist. An actual operation failure stays visible; stop only the operation that cannot proceed. Test assertions that distinguish correct from incorrect behavior are not runtime blockers.
By default, every development task has a finite time budget, including setup, tests, and reporting. Before a test run, estimate its duration from available timings and name the changed behavior it can prove or break. If timing is unknown, state an estimate; do not build an estimation system or run a preliminary suite. Use the smallest relevant command. By default, do not run full evaluation, unit, integration, or repository suites; propose one as a question to the owner. A skill, requirements document, reviewer, or default test command does not authorize them; a project may choose otherwise. Repeat only for a relevant change or failure. Remove checks that neither establish the requested main function nor expose its defects; reassurance is not a result.
Stop at the first rung that holds.
<input type="date"> over a picker lib, CSS over JS, a DB constraint over app code.Rules:
Output: code first, then at most three lines: what was skipped, when to add it. If the explanation is longer than the code, delete the explanation.
Read the diff and find what was over-built. Look for:
new/legacy branches, v2 beside v1, a flag guarding bothOne line each: file:L<n>: <what it is>. <what replaces it>. No essays.
End with net: -<N> lines possible. Nothing to cut: Lean already. Ship.
Keep input validation that prevents a concrete invalid operation at an actual trust boundary, error handling that prevents data loss, accessibility basics, and the smallest functional check. By default, there is no blanket security exemption. Keep what the user explicitly requested.
Report unrelated correctness or performance defects without expanding the task. Removing unnecessary security checks, blockers, runtime assertions, and hashes is part of this review. Cut lists; it applies fixes when the user asks for them.
Write the least code that works, and cut what an AI agent over-built. Use on any coding task: write, fix, refactor, or review a diff. Also when the user says 'less', 'simplify', 'too complex', 'over-e
---name: less-is-moredescription: Write the least code that works, and cut what an AI agent over-built. Use on any coding task: write, fix…---# skills/J-peer-review-and-audit/less-is-more/skill/SKILL.md概要
Write the least code that works, and cut what an AI agent over-built. Use on any coding task: write, fix, refactor, or review a diff. Also when the user says 'less', 'simplify', 'too complex', 'over-engineered', or 'what can we delete'. Not for prose, research, or non-code questions.
よくある質問
公開元から skills/J-peer-review-and-audit/less-is-more/skill/SKILL.md をダウンロードするか、パスをコピーしてリポジトリを開いてください。PlugMCP はスキルを掲載するだけで、ファイルはホストしていません。
公開元は https://github.com/sno-ai/sno-station-skills で管理しています。
Claude、Cursor、Codex、Grok Build は、公開元のリポジトリから追加した SKILL.md を読み込めます。Grok Bot は、チャットでスキルの GitHub フォルダーのリンクを送るとインストールします。