Demo data can hide layout failures, missing states, and incorrect formatting. This skill guides realistic fixture creation, development-only comparisons, and reports with targeted fixes.

Outdated Motoko examples can cause compiler errors and unsuitable backend designs. This skill provides modern language references, modular actor patterns, and mops dependency workflows.

Motoko migration errors can conflict with current source code and put deployed state at risk. This reference explains diagnostics and forward-only repairs while preserving migration history.

Motoko canister upgrades can fail or lose data when state changes do not match migration inputs and outputs. This skill guides compatible changes, self-contained migrations, and validation for enhanced migration chains.

Mixing product behavior with registry primitives makes component placement unclear and registry updates harder to manage. This skill guides alias resolution, ownership classification, and component placement with one-way dependencies.

Completion reports can overlook failing checks or untested changes. This skill guides ordered execution of existing project scripts and reports failures, missing checks, and unverified scope.

UI changes can introduce unnecessary browser code and inconsistent component boundaries. This skill guides framework detection, server-first implementation, explicit data states, and documented boundary decisions.

Astro development requires consistent routing, configuration, and deployment choices. This skill provides page examples, component patterns, CLI references, and adapter workflows linked to official documentation.

Frontend guidance becomes outdated as browser APIs and support levels change. This skill finds focused implementation guides with compatibility and fallback advice.

Code changes can miss acceptance criteria, repository rules, or security boundaries. This skill performs a read-only review and returns structured, line-anchored findings.

Multi-agent issue delivery can lose state, mix roles, and skip safeguards. This skill coordinates implementation, review, QA, escalation, and pull request creation through agent-flow.

Issue implementation can drift beyond scope or produce incomplete handoffs. This skill applies focused changes, runs project checks, commits once, and reports structured evidence.

Deferred work becomes difficult to track when its limits and upgrade triggers remain scattered across code comments. This skill collects marked comments into a ledger and flags missing triggers.

Unnecessary abstractions and redundant dependencies make repositories harder to maintain. This skill reviews the whole codebase and ranks deletion, simplification, and replacement opportunities.

Unnecessary abstractions and dependencies make small coding tasks harder to maintain. Ponytail guides your assistant toward existing helpers, standard libraries, and minimal changes while preserving essential safeguards.

AI skills often fail because triggers, structure, and validation are unclear. This guide provides practical patterns for reliable SKILL.md design, testing, and maintenance.

Project conventions are difficult to reproduce consistently across related repositories. This skill searches local references, cites sources, synchronizes mirrors, and summarizes workflow triggers.

Unclear prompts and crowded sessions reduce coding quality. This skill provides practical workflows for planning, verification, context control, automation, and independent review.

Matching Camel, Spring Boot, and CXF versions requires checking several release sources. This skill collects current metadata and creates one Markdown matrix.

Mobile app bugs and usability problems can remain hidden during routine checks. This skill guides exploratory testing with agent-device and captures runtime evidence for issues.