Run any Skill in Manus with one click

ponystack-ratio

Stars19

Forks1

UpdatedJune 18, 2026 at 15:25

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

AyanbekDos

AyanbekDos/ponystack

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

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

Thinking-to-diff ratio

Report the membrane's scoreboard for the work just done:

thinking : diff  =  <reasoning tokens>  :  <net code LOC>
ratio            =  <reasoning tokens / net code LOC>

Reasoning = tokens of thinking/planning spent this session (estimate from the conversation if exact counts are unavailable).
Net code LOC = non-blank, non-comment lines added inside code blocks / the diff. (Same counter the benchmark uses: 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.

More from this repository

same repository

ponystack-contract

AyanbekDos/ponystack

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.

2026-06-1819

ponystack

AyanbekDos/ponystack

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.

2026-06-1819

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

Thinking-to-diff ratio

Report the membrane's scoreboard for the work just done:

thinking : diff  =  <reasoning tokens>  :  <net code LOC>
ratio            =  <reasoning tokens / net code LOC>

Reasoning = tokens of thinking/planning spent this session (estimate from the conversation if exact counts are unavailable).
Net code LOC = non-blank, non-comment lines added inside code blocks / the diff. (Same counter the benchmark uses: benchmarks/loc.js.)

One line of verdict, then stop. This is a scoreboard, not an essay.