- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add jamditis/claude-skills-journalism --skill ponytail-dev -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add jamditis/claude-skills-journalism --skill ponytail-dev -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add jamditis/claude-skills-journalism --skill ponytail-dev -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add jamditis/claude-skills-journalism --skill ponytail-dev -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/jamditis/claude-skills-journalism/tree/HEAD/dev-toolkit/skills/ponytail-devFrom the publisher
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.
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.
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 under the MIT license.
Use to implement or review software with minimal code and proportional checks.
---name: ponytail-devdescription: Use to implement or review software with minimal code and proportional checks.---# dev-toolkit/skills/ponytail-dev/SKILL.mdFAQ
Download dev-toolkit/skills/ponytail-dev/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/jamditis/claude-skills-journalism.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.