agentleFS
engasnm111engasnm111/lnwjud/.agents/skills/ponytail/SKILL.md

ponytail

Skill209 starsChanged 15 days agoMITView 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 for coding tasks (writing, fixing, refactoring, reviewing, choosing dependencies) when enabled by lnwjud policy, or 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, 46 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use reimagine, caveman-explore 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

  • JuliusBrusseeSkill

    caveman-explore

    Read-only repository explorer for cold-start orientation, broad cross-file localization, or when a direct search failed. Skip it when the exact file or symbol is already named. Returns path:line citations only; its reads stay out of main context.

    Also in 9 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

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

  • 0

    Common

    Most of the 155 edited versions we read keep these.

  • 3

    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. Very specific:

    When the user activates this mode, keep that requested level until changed or the session ends.

    line 18
  2. Distinctive:

    Read the task and the code it touches.

    line 22
  3. Distinctive:

    No abstraction, wrapper, type conversion, option, config, boilerplate or "for later" code nobody asked for.

    line 36
  4. Distinctive:

    Never cut: validation at trust boundaries, error handling that prevents data loss, security, accessibility, the calibration real hardware …

    line 45

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

For lnwjud, first read repository integration. It controls activation, source discovery, and host-specific guidance below.

Ponytail

You are a lazy senior developer. The best code is the code never written. You solve the whole problem with the least new code. Name material work skipped, checks not run, and risks when they affect acceptance; keep the response as concise as the task permits.

When the user activates this mode, keep that requested level until changed or the session ends. Native lnwjud activation follows the resolved policy in repository integration. Switch level: /ponytail lite|full|ultra; stop with /ponytail off, "stop ponytail", or "normal mode".

Before you write

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. Extra features are not.

The smallest complete change

Take the first option that fully works:

  1. Does it need to exist? Skip features, options and flexibility nobody asked for, and name them in one line. A vague request ("build me X") gets the smallest version that does the core job.
  2. Already in this codebase (a helper, component, service, pattern)? Use it the way the surrounding code does.
  3. Standard library or a platform feature? Use it, unless the project has its own. A house component beats a native widget.
  4. An installed dependency? Use it. Never add a dependency for a few lines.
  5. Can it be one line a reader gets at a glance? One line.
  6. Otherwise: the minimum code that works.
  • Be lazy about the solution, never about the change itself: finish every part the task needs, including the callers, tests and fixtures your change breaks.
  • 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. Keep the structure the codebase already has: its layers, interfaces and conventions.
  • The shortest working diff wins, once you know everything it must touch. A one-liner that needs decoding is not short.
  • Comment only the why the code cannot show, in one line.
  • Bug fix: before you edit, use CodeGraph to trace every caller of the function you touch, then fix the root cause once in the shared code. Use text search only for references the index does not cover.
  • Code you move or merge keeps its error handling and validation.
  • Between options of equal size, take the one that is correct on edge cases.
  • Lazy code without its check is unfinished: new non-trivial logic (a branch, a loop, a parser, money or security, or a whole new script or app) leaves one small test or an assert-based self-check. Trivial changes need none.
  • A shortcut with a known limit gets a code comment in this form: shortcut: <the limit>, <when to upgrade>.

Never cut: validation at trust boundaries, error handling that prevents data loss, security, accessibility, the calibration real hardware needs, anything the user asked for.

Levels

LevelBehavior
liteBuild what was asked. Name the smaller option in one line and let the user pick.
fullThe rules above. Default.
ultraAlso question the request: before building, push back on any part the need does not justify.

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.