ponytail

Enforce minimal viable implementations using standard libraries and native features.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/marmelab/atomic-crm-demo-art-teaching --skill ponytail-marmelab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ponytail
Source: https://github.com/marmelab/atomic-crm-demo-art-teaching/tree/main/.claude/skills/ponytail
Command: npx skills add https://github.com/marmelab/atomic-crm-demo-art-teaching --skill ponytail-marmelab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the waste of over-engineered codebases, unnecessary dependencies, and effort spent on speculative features that never deliver value, freeing up development time for work that actually matters.

Core Features & Use Cases

  • YAGNI Enforcement: Automatically flags and skips speculative work that doesn't meet immediate needs.
  • Standard & Native First: Prioritizes built-in language standard library functions and native platform features over custom code or third-party dependencies.
  • Use Case: When asked to add a date selection field to a form, it will use a native date input instead of recommending a heavy third-party date picker library, cutting unnecessary bloat.

Quick Start

Use the ponytail skill to implement the requested feature using the shortest, simplest working solution that meets all requirements.

Frequently Asked Questions about ponytail

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent over-engineering when implementing new software features?

Reduce technical debt by enforcing minimal viable implementation and prioritizing built-in standard library functions over custom code. This approach eliminates unnecessary bloat and skips speculative work that doesn't meet immediate requirements.

How do I reduce external dependencies when adding UI components like a date picker?

Reduce external dependencies by prioritizing native platform features and built-in standard library functions over third-party libraries. For example, use a native date input instead of installing a heavy custom date picker package to cut unnecessary bloat.

What is the best way to refactor code to minimize technical debt?

The best way to minimize technical debt during refactoring is to enforce code simplicity through standard-library-first principles. Automatically flag and skip speculative work, ensuring you ship the shortest, simplest working solution that meets all requirements.

Does YAGNI enforcement work for both bug fixes and feature implementation?

YAGNI enforcement works across software development tasks including feature implementation, bug fixes, and refactoring. It automatically flags and skips speculative work, prioritizing standard tooling and minimal code to satisfy immediate requirements without over-engineering.

When should I avoid using the standard library over a third-party dependency?

Avoid standard-library-first principles only when native platform features cannot meet specific, immediate requirements. If built-in functions lack necessary capabilities for the current task, introducing a third-party dependency becomes justified rather than speculative bloat.