菜单
Thinking-to-diff ratio (Seam 3): reasoning spent divided by net code shipped. The membrane's scoreboard - a high ratio means the thinking went into the plan, not the line count. Use when the user says "ratio", "thinking-to-diff", "score this session", or invokes /ponystack-ratio.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
The contract gate (Seam 2). Closes a wide pass by cutting it to the minimum that works: reinvented stdlib, speculative abstractions, dead flexibility, one-caller layers. One line per finding, ends with the only number that matters. Use after a thorough plan or implementation, or when the user says "contract this", "cut it down", "what can we delete", "expand-contract", or invokes /ponystack-contract.
The membrane between an expensive brain and cheap hands. Boil the lake to understand a problem; do not pour it into your code. Think expensive, write cheap. A phase router mutes the lazy senior while you plan and unleashes it while you implement. Use whenever the user says "ponystack", "membrane", "think expensive write cheap", complains that a process bloats the code, or wants gstack's thoroughness without gstack's line count.
| name | ponystack-ratio |
| description | Thinking-to-diff ratio (Seam 3): reasoning spent divided by net code shipped. The membrane's scoreboard - a high ratio means the thinking went into the plan, not the line count. Use when the user says "ratio", "thinking-to-diff", "score this session", or invokes /ponystack-ratio. |
| license | MIT |
Report the membrane's scoreboard for the work just done:
thinking : diff = <reasoning tokens> : <net code LOC>
ratio = <reasoning tokens / net code LOC>
benchmarks/loc.js.)A high ratio is the champion: deep understanding, narrow output. Example to
celebrate: 9,000 : 11 → ratio 818. A low ratio is the warning sign:
lots of code, little thought - the lake got poured into the diff.
One line of verdict, then stop. This is a scoreboard, not an essay.