Quality

API Design Patterns provides conventions and best practices for designing consistent REST APIs. Use it when creating endpoints, reviewing contracts, handling pagination, error responses, status codes, filtering, or versioning.

Benchmark measures performance baselines, detects regressions before and after PRs, and compares stack alternatives for pages, APIs, and builds.

Benchmark Optimization Loop turns vague performance goals into a bounded, measured optimization process. Use it when asked to make something faster, benchmark latency/throughput/cost, or choose the best implementation by repeated measured tests.

Agent Self-Evaluation rates an agent's own output on five axes—accuracy, completeness, clarity, actionability, and conciseness—with evidence per criterion. Use it after completing any non-trivial task to catch omissions and surface improvements before the user has to.

AI Regression Testing provides testing patterns for AI-assisted development, catching blind spots when the same model writes and reviews code. Use it for sandbox-mode API tests and regression coverage after AI code changes.

Web Application Testing verifies and debugs local web applications using Playwright. It supports frontend functional testing, screenshot capture, browser log viewing, and UI automation.

Ponytail Debt scans a codebase for `ponytail:` comments and reports them as a debt ledger, so deferred shortcuts are tracked instead of forgotten, and flags markers with no upgrade trigger.

Ponytail Review reviews a code diff for over-engineering and flags what to delete: reinvented standard library functions, needless dependencies, speculative abstractions, and verbose code. Use it to keep changes lean and minimal.

Ponytail Audit scans a whole repository for over-engineering and ranks findings—dead code, standard-library or native replacements, YAGNI abstractions, and shrink opportunities—so you can decide what to delete or simplify. Use it when asked to audit a codebase, find bloat, or identify removable complexity.

Ponytail Audit scans a repository for over-engineering and returns a ranked list of what to delete, simplify, or replace with standard library or native features. Use it before a code review to identify dead code, unnecessary abstractions, and duplicated platform functionality.

Ponytail Debt scans a codebase for `ponytail:` comments and compiles them into a debt ledger, flagging entries with no trigger as rot risks. Use it when asked to list shortcuts or review what was deferred, as a one-shot report that changes nothing.

Ponytail Review flags over-engineering in code diffs: dead code, reinvented standard library functions, unneeded dependencies, and speculative abstractions. Use it when asking for a simplicity review or 'what can we delete'.