// 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.
| 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 |
| 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 |
| 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 |
Load the Pony language reference (capabilities, PonyCheck, stdlib pitfalls, mort pattern). Load it before Pony coding sessions.
Ensemble code review with specialized reviewer personas. Has full (8-persona) and lightweight (3-persona) modes. Load when conducting a code review of a PR, branch, or local changes.
Ensemble documentation review with specialized reviewer personas. Has full (8-persona) and lightweight (3-persona) modes. Load when reviewing documentation-only changes where code-focused personas don't apply.
Ensemble workflow for producing higher-confidence outputs through decorrelated reasoning paths. Load when the human explicitly requests the ensemble approach.
Property-based and generative testing patterns. Load when writing property-based tests, generators, or generative test suites.
Disciplines for software design work. Load when designing APIs, type systems, features, or system boundaries. Counters the tendency to retrieve familiar patterns instead of discovering what the problem actually needs. Has full (8-persona) and lightweight (5-persona) modes.