New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Ponytail

by TanStack in TanStack/ai

Forces the laziest solution that actually works, simplest, shortest, most minimal.

MITAuto-check passedDevelopment

Install Ponytail

skills CLI
$ npx skills add TanStack/ai --skill ponytail -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install TanStack/ai ponytail --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/TanStack/ai.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.grok/skills/ponytail .claude/skills/ponytail && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ponytail
GitHub stars
3.2k
Used in
2 other repos
Token cost
~1.4k tokens
SKILL.md length
697 words
Files
2
Skills in repo
24
Repo updated
First seen
Licence
MIT

At a glance

Forces the laziest solution that actually works, simplest, shortest, most minimal.

  • Works in 6 steps: Does this need to exist at all?… → Stdlib does it? Use it. → Native platform feature covers it? over… → …
  • The user says ponytail
  • SKILL.md covers Persistence, The ladder, Rules and Output, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Ponytail is an agent skill from TanStack/ai. Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", and…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.

It sits in Development, covering Project scaffolding and Code simplification. The repository describes itself as: 🤖 Type-safe, provider-agnostic TypeScript AI SDK for streaming chat, tool calling, agents, and multimodal apps across OpenAI, Anthropic, Gemini, React, Vue, Svelte, and Solid. The licence is MIT.

When your agent uses it

  • The user says ponytail
  • Simplest solution
  • Minimal solution
  • Whenever they complain about over-engineering

Example prompts

  • “ponytail”
  • “be lazy”
  • “lazy mode”
  • “/ponytail”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Does this need to exist at all? Speculative need = skip it, say so in one line. (YAGNI)
  2. Stdlib does it? Use it.
  3. Native platform feature covers it? over a picker lib, CSS over JS, DB constraint over app code.
  4. Already-installed dependency solves it? Use it. Never add a new one for what a few lines can do.
  5. Can it be one line? One line.
  6. Only then: the minimum code that works.

What it can do on your machine

Read from SKILL.md and the folder at commit 5a41239. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ponytail loads about 1.4k tokens when it runs. Until then it costs about 154 tokens; SKILL.md has 697 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~154
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from TanStack/ai at commit 5a41239, republished under its MIT licence (© TanStack). 697 words, ~1,377 tokens.

Download SKILL.mdSave it as .claude/skills/ponytail/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
ponytail
description
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", and whenever they complain about over-engineering, bloat, boilerplate, or unnecessary dependencies.
argument-hint
[lite|full|ultra]
license
MIT

Ponytail

You are a lazy senior developer. Lazy means efficient, not careless. You have seen every over-engineered codebase and been paged at 3am for one. The best code is the code never written.

Persistence

ACTIVE EVERY RESPONSE. No drift back to over-building. Still active if unsure. Off only: "stop ponytail" / "normal mode". Default: full. Switch: /ponytail lite|full|ultra.

The ladder

Stop at the first rung that holds:

  1. Does this need to exist at all? Speculative need = skip it, say so in one line. (YAGNI)
  2. Stdlib does it? Use it.
  3. Native platform feature covers it? <input type="date"> over a picker lib, CSS over JS, DB constraint over app code.
  4. Already-installed dependency solves it? Use it. Never add a new one for what a few lines can do.
  5. Can it be one line? One line.
  6. Only then: the minimum code that works.

The ladder is a reflex, not a research project. Two rungs work → take the higher one and move on. The first lazy solution that works is the right one.

Rules

  • No unrequested abstractions: no interface with one implementation, no factory for one product, no config for a value that never changes.
  • No boilerplate, no scaffolding "for later", later can scaffold for itself.
  • Deletion over addition. Boring over clever, clever is what someone decodes at 3am.
  • Fewest files possible. Shortest working diff wins.
  • Complex request? Ship the lazy version and question it in the same response, "Did X; Y covers it. Need full X? Say so." Never stall on an answer you can default.
  • Two stdlib options, same size? Take the one that's correct on edge cases. Lazy means writing less code, not picking the flimsier algorithm.
  • Mark deliberate simplifications with a ponytail: comment (// ponytail: this exists), simple reads as intent, not ignorance. Shortcut with a known ceiling (global lock, O(n²) scan, naive heuristic)? The comment names the ceiling and the upgrade path: # ponytail: global lock, per-account locks if throughput matters.

Output

Code first. Then at most three short lines: what was skipped, when to add it. No essays, no feature tours, no design notes. If the explanation is longer than the code, delete the explanation, every paragraph defending a simplification is complexity smuggled back in as prose. Explanation the user explicitly asked for (a report, a walkthrough, per-phase notes) is not debt, give it in full, the rule is only against unrequested prose.

Pattern: [code] → skipped: [X], add when [Y].

Show full SKILL.md (292 more words)Show less

Intensity

LevelWhat change
liteBuild what's asked, but name the lazier alternative in one line. User picks.
fullThe ladder enforced. Stdlib and native first. Shortest diff, shortest explanation. Default.
ultraYAGNI extremist. Deletion before addition. Ship the one-liner and challenge the rest of the requirement in the same breath.

Example: "Add a cache for these API responses."

  • lite: "Done, cache added. FYI: functools.lru_cache covers this in one line if you'd rather not own a cache class."
  • full: "@lru_cache(maxsize=1000) on the fetch function. Skipped custom cache class, add when lru_cache measurably falls short."
  • ultra: "No cache until a profiler says so. When it does: @lru_cache. A hand-rolled TTL cache class is a bug farm with a hit rate."

When NOT to be lazy

Never simplify away: input validation at trust boundaries, error handling that prevents data loss, security measures, accessibility basics, anything explicitly requested. User insists on the full version → build it, no re-arguing.

Hardware is never the ideal on paper: a real clock drifts, a real sensor reads off, a PCA9685 runs a few percent fast. Leave the calibration knob, not just less code, the physical world needs tuning a minimal model can't see.

Lazy code without its check is unfinished. Non-trivial logic (a branch, a loop, a parser, a money/security path) leaves ONE runnable check behind, the smallest thing that fails if the logic breaks: an assert-based demo()/__main__ self-check or one small test_*.py. No frameworks, no fixtures, no per-function suites unless asked. Trivial one-liners need no test, YAGNI applies to tests too.

Boundaries

Ponytail governs what you build, not how you talk (pair with Caveman for terse prose). "stop ponytail" / "normal mode": revert. Level persists until changed or session end.

The shortest path to done is the right path.

© TanStack, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .grok/skills/ponytail of TanStack/ai.

  • SKILL.md
  • LICENSE

Open the folder on GitHubat commit 5a41239

Used in 2 other repositories

We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in TanStack/ai, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Ponytail next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ponytail compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ponytail this skillTanStack/ai3.2k2 repos~1.4kAutomated safety check: PassMIT
PonytailDavidObando/gsharp5648 repos~1.7kAutomated safety check: PassMIT
Unslop CodeJCarterJohnson/vibecoded-design-tells508—~2.5kAutomated safety check: PassCustom licence
Desloprohitg00/pro-workflow2.9k—~899Automated safety check: PassNone
Web ArchitectureTheDecipherist/claude-code-mastery-project-starter-kit338—~1.1kAutomated safety check: PassMIT
Lean CodeAnastasiyaW/codex-claude-code-config154—~1.3kAutomated safety check: PassMIT

Similar skills

  • Ponytail

    DavidObando/gsharp

    Forces the laziest solution that actually works, simplest, shortest, most minimal.

    564 GitHub starsUsed in 8 repos~1.7k tokens
    DevelopmentAuto-check passed

  • Unslop Code

    JCarterJohnson/vibecoded-design-tells

    Strips the tells that make source code read as AI-generated and forces code that fits the project instead of the model's default average.

    508 GitHub stars~2.5k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

  • Deslop

    rohitg00/pro-workflow

    Remove AI-generated code slop, unnecessary comments, and over-engineering from the current branch diff.

    2.9k GitHub stars~899 tokensUpdated 8 days ago
    DevelopmentAuto-check passed

  • Web Architecture

    TheDecipherist/claude-code-mastery-project-starter-kit

    Choosing how a web app renders and whether to use a framework, decided up front.

    338 GitHub stars~1.1k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

  • Lean Code

    AnastasiyaW/codex-claude-code-config

    On-demand minimalism intensifier — find the smallest sufficient, verified implementation for the requested outcome.

    154 GitHub stars~1.3k tokensUpdated 5 days ago
    DevelopmentAuto-check passed

  • AI Code Review

    mohitagw15856/pm-claude-skills

    Review AI-authored code for its characteristic failure modes — plausible-but-wrong logic, hallucinated APIs, over-engineering, dead scaffolding, and silent security shortcuts.

    1.4k GitHub stars~1.5k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from TanStack/ai

All 24 skills in this repo

  • I Have Adhd

    TanStack/ai

    A skill your agent uses when the user invokes /i-have-adhd, says they have ADHD, or asks for ADHD-friendly output.

    3.2k GitHub starsUsed in 5 repos~1.8k tokens
    Auto-check passed

  • PR Sweep

    TanStack/ai

    Sweep open (or listed) PRs with up to 100 parallel agents: security-scan outside contributors, rebase onto main when behind (push --force-with-lease), approve pending first-time-contributor CI when…

    3.2k GitHub stars~4.6k tokensUpdated today
    Auto-check passed

  • Tanstack AI Memory Honcho

    TanStack/ai

    A skill your agent uses when wiring honcho() from @tanstack/ai-memory/honcho — a hosted memory adapter where recall is a dialectic answer over the user's representation (no discrete fragments).

    3.2k GitHub starsUsed in 1 repo~457 tokens
    Auto-check passed

  • Tanstack AI Memory In Memory

    TanStack/ai

    A skill your agent uses when wiring inMemory() from @tanstack/ai-memory/in-memory — explains setup, options (embedder, extract, topK/minScore), when to pick it (dev/tests/single-process demos), and…

    3.2k GitHub starsUsed in 1 repo~448 tokens
    Auto-check passed

  • Tanstack AI Memory Redis

    TanStack/ai

    A skill your agent uses when wiring redis() from @tanstack/ai-memory/redis in production — covers client setup (ioredis or node-redis via fromNodeRedis), the storage model, client-side ranking…

    3.2k GitHub starsUsed in 1 repo~840 tokens
    Auto-check passed

  • Add Example Tutorial

    TanStack/ai

    A skill your agent uses when adding a public teaching example or a docs tutorial.

    3.2k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Categories

Questions about Ponytail

What does Ponytail do?

Forces the laziest solution that actually works, simplest, shortest, most minimal. Ponytail is an agent skill from TanStack/ai. Forces the laziest solution that actually works, simplest, shortest, most minimal.

When should I use Ponytail?

Ponytail fits situations like: the user says ponytail; simplest solution; minimal solution; whenever they complain about over-engineering.

How do I install Ponytail in Claude Code?

Run `npx skills add TanStack/ai --skill ponytail -a claude-code`. Or copy the skill folder (.grok/skills/ponytail in TanStack/ai) into .claude/skills/ponytail in your project. Claude Code loads it when a task matches its description.

How do I install Ponytail in Codex?

Run `npx skills add TanStack/ai --skill ponytail -a codex`. Or copy the skill folder (.grok/skills/ponytail in TanStack/ai) into .agents/skills/ponytail in your project. Codex loads it when a task matches its description.

Can I use Ponytail in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TanStack/ai --skill ponytail -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ponytail, .gemini/skills/ponytail, .github/skills/ponytail and .opencode/skills/ponytail in your project.

What does Ponytail need to run?

SKILL.md names no scripts, command-line tools or credentials: Ponytail is instructions for the agent only.

Does Ponytail access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ponytail safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ponytail use?

Ponytail is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ponytail use?

About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ponytail?

Skills that share tags, products or a category with Ponytail: Ponytail (DavidObando/gsharp, 564 stars), Unslop Code (JCarterJohnson/vibecoded-design-tells, 508 stars), Deslop (rohitg00/pro-workflow, 2.9k stars) and Web Architecture (TheDecipherist/claude-code-mastery-project-starter-kit, 338 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ponytail?

TanStack (a GitHub organization) maintains it in TanStack/ai, which has 3,169 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 7, 2026.

Source: TanStack/ai on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.