Patronum Skill
Use this skill to solve Patronum usage questions quickly and consistently. Target Patronum v2.x by default.
Workflow
- •Classify request:
- •
operator-choice: choose one or several operators for a task. - •
api-explain: explain signature, overloads, and return value. - •
compose: combine multiple operators into one flow. - •
debug: usedebugand scope-aware debugging notes. - •
migration: map legacy forms to modern usage.
- •Load references progressively:
- •Start with
references/operator-matrix.md. - •Add
references/recipes.mdfor task-to-solution mapping. - •Add
references/pitfalls.mdfor caveats and anti-patterns. - •Add
references/migration-notes.mdwhen legacy forms appear.
- •Build answer contract:
- •Start with decision: selected operator(s) and why.
- •Provide minimal practical snippet.
- •Add caveats (imports, overload differences, behavior traps).
- •For uncertain versions, explicitly state v2 assumption and show migration note.
Defaults
- •Prefer Patronum v2.x shorthand where available.
- •Prefer concise examples with explicit imports.
- •Keep examples deterministic and composable with Effector primitives.
- •Prefer
patronum/<operator-kebab-name>imports when clarity matters.
Guardrails
- •Do not suggest outdated signatures as default.
- •Do not invent operators outside the official list.
- •Do not hide behavior differences between overloads.
- •Do not skip edge cases for
pending,condition,interval,time, anddebug.
Output Template
Use this structure in answers:
- •
Use <operator>: one-line reason. - •
Example: minimal code block. - •
Caveats: version or overload notes.