菜单
Show the lazy piggy version and the verbose from-scratch version of the same code side by side, so the tradeoff is visible instead of taken on faith. Use when the user says "compare versions", "show me both ways", "piggy compare", "/piggy-compare", or "what would this look like without piggy".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Audit the whole repo for over-engineering. A ranked list of what to delete, simplify, or replace with stdlib or native features.
Harvest every piggy: shortcut comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.
Show piggy measured impact as a scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display.
Quick reference for piggy's modes, skills, and commands. One-shot display.
Review a diff for over-engineering. Finds what to delete: reinvented stdlib, needless deps, speculative abstractions. One line per finding.
Lazy senior dev mode for any coding task (write, refactor, fix, review): YAGNI, stdlib first, no unrequested abstractions. Not for non-coding requests.
| name | piggy-compare |
| description | Show the lazy piggy version and the verbose from-scratch version of the same code side by side, so the tradeoff is visible instead of taken on faith. Use when the user says "compare versions", "show me both ways", "piggy compare", "/piggy-compare", or "what would this look like without piggy". |
Produce both implementations of the same request — the piggy (lazy, ladder- enforced) version and the verbose (from-scratch, no ladder) version — so the reader can see exactly what the ladder skipped and judge the tradeoff themselves.
## Lazy (piggy)
<the shortest version that works, ladder-enforced>
## Verbose (no piggy)
<the version piggy would replace: hand-rolled, no stdlib/native shortcuts>
## Diff
lines: <lazy line count> vs <verbose line count>
skips: <what the verbose version adds that the lazy one doesn't need — extensibility hooks, config surface, edge cases the ticket didn't ask for>
ceiling: <what would force the lazy version to grow toward the verbose one>
Both versions must actually work — this isn't a strawman verbose version built to lose, it's what a careful engineer would ship without the ladder.
## Lazy (piggy)
const isValidEmail = (s) => /\S+@\S+\.\S+/.test(s);
## Verbose (no piggy)
class EmailValidator {
constructor(opts = {}) { this.strict = opts.strict ?? false; }
validate(s) {
if (!s || typeof s !== 'string') return false;
const parts = s.split('@');
if (parts.length !== 2) return false;
const [local, domain] = parts;
if (!local.length || !domain.includes('.')) return false;
if (this.strict) { /* RFC 5322 checks */ }
return true;
}
}
## Diff
lines: 1 vs 12
skips: a strict RFC 5322 mode nobody asked for, a class for one method
ceiling: real deliverability still needs a confirmation email either way
Shows both, applies neither — the user decides which to keep. For why the
lazy one was picked, point to /piggy-explain. Read-only.
"stop piggy-compare" or "normal mode" to revert.