Programming · Building & coding
ponytail-dev
/ponytail-dev
Use to implement or review software with minimal code and proportional checks.
For whom
- Author
- jamditis ↗
- Repository
- claude-skills-journalism ↗
- Licence
- MIT
- Last repository change
- 24.10.2026
Assessment and security
81/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability21 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content20 / 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
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
Deprecation
No signals detected. Repository changed on 24.10.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
Use to implement or review software with minimal code and proportional checks.
Original author description
Use to implement or review software with minimal code and proportional checks.
How it works
- Verification
- Boundaries
Original SKILL.md headings · 46 lines, 259 words
SKILL.md preview
--- name: ponytail-dev description: Use to implement or review software with minimal code and proportional checks. license: MIT --- # Ponytail dev Use this skill for software implementation, fixes, refactoring, infrastructure, tests, and technical review. In mixed work, treat the approved design as fixed input and apply this skill only to implementation. Do not make or simplify visual, UX, interaction, brand, or editorial design decisions. Do not reduce design quality to save code. Understand the affected flow before choosing a change. Prefer an existing pattern, the standard library, native platform features, or an installed dependency. Add only the code that the current requirement needs. Avoid speculative abstractions, compatibility layers, configuration, and extension points. For a bug, find the root cause and inspect relevant callers. Fix a shared cause when the evidence supports that scope. ## Verification Use the smallest evidence that proves the result. Prefer an existing relevant test, focused command, build, type check, linter, temporary probe, or direct behavior check. Run broader checks when the changed scope, risk, repository rules, or CI behavior requires them. Add a persistent test when it protects a likely repeat failure, stable public contract, non-obvious logic, or high-impact behavior. Static and trivial edits usually need direct inspection only. ## Boundaries Do not simplify away security controls, trust-boundary validation, data-loss protection, required error handling, accessibility, or an explicit requirement. Match the proof to the impact, uncertainty, and recovery cost. Keep the handoff short. State the change, the evidence, and any known limit that affects the user's decision. Related skills: `vibe-coding` (dev-toolkit) covers broader AI-assisted development, and `verification-before-completion` (superjawn) covers final proof before a completion claim. Credit: Adapted from [DietrichGebert/ponytail](https://github.com/DietrichGebert/ponytail) under the MIT license.
Files in this package (3)
- LICENSE 1 KB
- SKILL.md 2 KB
- agents/openai.yaml 1 KB
Versions
The database has no other skills named ponytail-dev.
Database snapshot: 13.11.2026 · package version 8fa883241036 (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
- 85ponytail-debt
List every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. - 85ponytail-debt
List every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. - 85ponytail-debt
List every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. - 100ponytail
Lazy senior dev mode for coding work: ship the smallest change that fully solves the task, reuse what the codebase, stdlib, platform or installed dependencies already provide, keep validation, data-loss handling, security and accessibility, leave one small check for risky logic,… - 100ponytail
Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Enforces YAGNI, standard library reuse, native platform features, and minimal diffs. Use on any coding task (writing, fixing, refactoring, reviewing, choosing… - 85ponytail-debt
Harvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into "later means never". Use when the user says "ponytail debt", "/core:ponytail-debt", "what did ponytail…