Skip to content
Skills Library
Programming · Review & audit

ponystack-contract

/ponystack-contract

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.

Repository
ponystack ↗
Licence
MIT
Last repository change
18.06.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 18.06.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Triggers from the description

contract thiscut it downwhat can we deleteexpand-contract
Original author description

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.

How it works

  1. Format
  2. Scoring
  3. Boundaries
Original SKILL.md headings · 31 lines, 172 words
SKILL.md preview
---
name: ponystack-contract
description: >
  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.
license: MIT
---

# Contract gate

You (or gstack) just boiled the lake. Now the membrane closes. Review the diff
(or the proposed plan) for everything that does not earn its lines.

## Format

`L<line>: <tag> <what>. <replacement>.` - or `<file>:L<line>: ...` across files.

Tags:

- `delete:` dead code, unused flexibility, speculative feature. Replacement: nothing.
- `stdlib:` hand-rolled thing the standard library ships. Name the function.
- `native:` dependency or code doing what the platform already does. Name the feature.
- `yagni:` abstraction with one implementation, config nobody sets, layer with one caller.
- `shrink:` same logic, fewer lines. Show the shorter form.

## Scoring

End with the only metric that matters: `net: -<N> lines possible.`
If there is nothing to cut: `Lean already. Ship.` and stop.

## Boundaries

Complexity only. Correctness bugs, security holes, and performance go to a
normal review pass (in `review` phase ponystack runs both). Never flag the one
mandatory runnable check as bloat. Never cut trust-boundary validation,
data-loss handling, security, or accessibility. Lists findings; does not apply
them unless asked.

Versions

The database has no other skills named ponystack-contract.

Database snapshot: 13.11.2026 · package version 3ca5af8f42dc (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100ponytail-review
    Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for…
  • 100ponytail-review
    Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for…
  • 100ponytail-review
    Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for…
  • 100ponytail-review
    Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for…
  • 100ponytail-review
    Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for…
  • 100ponytail-review
    Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.