agentleFS
Sign inStart free
contactandrewchl-wqcontactandrewchl-wq/turtle-mcp/skills/ponytail/SKILL.md

ponytail

Skill2 starsChanged 5 months agoMITView on GitHub

Anti-sobre-ingeniería. Antes de escribir código, recorré la escalera de decisión: ¿debe existir? → ¿hay biblioteca estándar? → ¿hay característica nativa? → ¿se resuelve en una línea? → mínimo viable. Marca atajos con un comentario que nombre su ruta de mejora.

154 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use reimagine, herdr-cli and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dev-willbird1936Skill

    reimagine

    Rebuild an instruction file for reliable adherence and lower context cost. Use when explicitly asked to reimagine or restructure-and-compress a prompt, skill or rules file.

    Also in 3 projects that use this

  • julweberSkill

    herdr-cli

    Expert guide for herdr, the terminal workspace manager for AI coding agents.

    Also in 3 projects that use this

  • vikas8520-coderSkill

    cli-backup-sync

    Backup and restore Nerve data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.

    Also in 3 projects that use this

  • vikas8520-coderSkill

    cli-batches

    Submit and monitor batch inference jobs from the CLI. Upload and manage files for batch processing, retrieve results, and integrate batch pipelines with CI/CD workflows.

    Also in 3 projects that use this

  • +8 more from vikas8520-coder

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 149 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No introduzcas abstracciones por "futura flexibilidad".

    line 38
  2. Very specific:

    No agregues banderas/features/configs por escenarios que aún no pasan.

    line 39

“Common” is measured: kept by at least 6 in 10 of the 149 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ponytail

Atá la solución corta antes de soltarla larga. Cada vez que vayas a escribir código, bajá por esta escalera y parate en el primer escalón que resuelva el problema.

Escalera de decisión

  1. ¿Debe existir? Si nadie lo va a usar más de una vez, probablemente no.
  2. Biblioteca estándar. Si lo trae el lenguaje, usalo. Sin envoltorios.
  3. Característica nativa del framework. Si el framework ya lo hace, dejalo.
  4. Una línea. ¿Se resuelve con una expresión? Hacelo.
  5. Mínimo viable. Lo más simple que funcione para el caso real, no para el imaginado.

Reglas de atajo

  • Si tomás un atajo, comentalo con su ruta de mejora:

    // atajo: validar en cliente; mover a backend si se reutiliza

  • No introduzcas abstracciones por "futura flexibilidad". Tres usos antes de extraer.
  • No agregues banderas/features/configs por escenarios que aún no pasan.

Niveles

  • lite — solo la escalera, sin marcar atajos.
  • full — escalera + atajos comentados (por defecto).
  • ultra — además, rechazá cualquier abstracción nueva sin tres casos reales.
  • off — desactivada.

Cuándo NO aplicar

  • Bordes del sistema (entrada de usuario, API pública): ahí sí validás y abstraés.
  • Código crítico de seguridad: la simplicidad no justifica saltar verificaciones.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free