一键导入
pony-skills
Routing index for the Pony skills — tells you which pony-* skill to load for each task, and when. Load at the start of work in a Pony project.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Routing index for the Pony skills — tells you which pony-* skill to load for each task, and when. Load at the start of work in a Pony project.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | pony-skills |
| description | Routing index for the Pony skills — tells you which pony-* skill to load for each task, and when. Load at the start of work in a Pony project. |
| disable-model-invocation | false |
When one of these applies, load the named skill.
| When | Load |
|---|---|
| Working on Pony at all — before you start, and for questions about capabilities, the type system, the runtime, or testing | pony-ref |
Writing any prose that ships with the code — a comment, docstring, release note, README, AGENTS.md, issue, PR description, or commit message | pony-prose |
| Before writing or changing a comment or docstring | pony-comments |
Before writing or changing a project's AGENTS.md or CLAUDE.md | pony-agents-md |
| Designing APIs, types, features, or system boundaries (not just implementing an existing design) | pony-software-design |
| Reviewing code, or before opening a PR | pony-code-review |
| Reviewing a documentation-only change | pony-docs-review |
| A problem you notice while working on something else — decide whether it belongs in your change, and if not, capture it and vet it before filing an issue | pony-vet-suspected-issues |
| Writing tests, or assessing test quality | pony-test-design |
| Writing property-based or generative tests | pony-pbt-patterns |
| Before forming a hypothesis about a non-trivial bug | pony-debug |
Making a user-facing change in a released project (VERSION is not 0.0.0) | pony-release-notes |
| Writing or updating a library's README | pony-library-readme |
| Adding, updating, or reorganizing examples | pony-examples-readme |
| Running the ensemble workflow (on request) | pony-ensemble |
How the words go in a comment, docstring, release note, README, or a project's AGENTS.md — write plainly, say the fact, and stop. Load before writing any prose that ships with the code. Language-agnostic.
Structured debugging protocol with checkpoints. Load when debugging non-trivial issues — before forming any hypothesis about the cause.
Load the Pony language reference (capabilities, PonyCheck, stdlib pitfalls, mort pattern). Load it before Pony coding sessions.
What belongs in a project's AGENTS.md and what never does. Load before writing or changing AGENTS.md or CLAUDE.md. Language-agnostic.
Ensemble code review with specialized reviewer personas. Has full (9-persona) and lightweight (4-persona) modes. Load when conducting a code review of a PR, branch, or local changes.
What earns a comment, what never belongs in one, and what to do when two distant things must change together. Load before writing or changing any comment or docstring. Language-agnostic.