agentleFS
mvsimaomvsimao/agent-skills/.agents/skills/ponytail/SKILL.md

ponytail

Skill2 starsChanged 7 days agoNo licenceView on GitHub

Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.

160 other projects use a version of this, 26 of them edited; 7 of 26 edited versions we compared changed its rules; 9 new projects in the last 4 weeks, against 7 the 4 before.

How people change it

7 of 26 edited versions changed its rules, and some changes recur.

Of the 26 edited versions we compared: 19 keep every rule, 7 made changes of their own.

Rules people drop

  1. Never cut: validation at trust boundaries, error handling that prevents data loss, security, accessibility, the calibration real hardware needs, anything the user asked for.dropped by 5 of 7
  2. Read the task and the code it touches. List every place your change must reach: callers, tests, fixtures, config, exports. Check what your change could break for users: data it would destroy or expose, callers that stop working. That is scope. …dropped by 3 of 7
  3. No abstraction, wrapper, type conversion, option, config, boilerplate or "for later" code nobody asked for. Keep values in the form the platform already gives you. Deletion beats addition. …dropped by 2 of 7

Rules people add

  1. Read the task and the code it touches. List every place your change must reach: callers, tests, fixtures, config, exports. Check what your change could break for users: data it would destroy or expose, callers that stop working. That is scope. …added by 3 of 7
  2. Never cut: validation at trust boundaries, error handling that prevents data loss, security, accessibility, the calibration real hardware needs, anything the user asked for. User insists on the full version → build it, no re-arguing.added by 2 of 7
  3. Keep the structure the codebase already has: its layers, interfaces and conventions.added by 2 of 7
  4. Standard library or platform feature? Use it, unless the project has its own (a house component beats a native widget). On Windows + Node: node:fs, node:path, node:test before a package.added by 2 of 7
  5. An installed dependency? Use it. Never add a dependency for a few lines.added by 2 of 7

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Rising: 9 new projects took it in the last 4 weeks, 1.3× the 4 weeks before.

Week of Sep 20: 0 new projectsWeek of Sep 27: 1 new projectWeek of Oct 4: 3 new projectsWeek of Oct 11: 3 new projectsWeek of Oct 18: 1 new projectWeek of Oct 25: 3 new projectsWeek of Nov 1: 3 new projectsWeek of Nov 8: 2 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read.

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

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 135 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 135 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.

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.