minecraft-paper-plugins

name	minecraft-paper-plugins
description	Use when creating, reviewing, validating, or migrating Paper-first Minecraft server plugins, including Bukkit/Paper API usage, events, commands, lifecycle, scheduling, Folia-sensitive code, and server-version compatibility. Prefer this skill whenever the user asks for Paper, Spigot-compatible plugin, Bukkit event, or server plugin development help.

Minecraft Paper Plugins

Use this skill for Paper-first plugin development. Treat Bukkit and Spigot APIs as compatibility layers, and prefer Paper documentation when Paper-specific behavior matters.

Workflow

1. Resolve the target Minecraft/Paper version if the user asks for version-specific behavior.
2. Read references/sources.md before citing plugin API or event facts.
3. Use the minecraft-skills CLI for machine-verifiable facts.
4. Use minecraft-skills plugin paper search "<task>" before broad list commands when you need to find relevant recipes, intents, guardrails, diagnostics, claim policies, fact surfaces, source tiers, datasets, or version-support entries.
5. Use minecraft-skills plugin paper intents to choose the exact lookup path for the user's intent.
6. Use minecraft-skills plugin paper recipes to choose an ordered workflow for listener, API, scheduler, or Folia-sensitive code.
7. Use minecraft-skills plugin paper search-scenarios "<task>" to route user wording to an existing scenario without inventing one.
8. Use minecraft-skills plugin paper scenarios when you need all realistic evaluation cases for the domain.
9. After choosing a scenario, use minecraft-skills plugin paper plan <scenario-id> <version> to resolve the exact recipes, intent lookups, diagnostics, claim policies, fact surfaces, response patterns, and evidence required for that task.
10. Use minecraft-skills plugin paper context <version> when you need preflight, intent routing, and evidence in one payload.
11. Use minecraft-skills plugin paper guardrails and minecraft-skills plugin paper diagnostics before finalizing generated plugin code.
12. Use minecraft-skills plugin paper claim-policies before making Paper support, API, event, or Folia/thread-safety claims.
13. Use minecraft-skills plugin paper output-requirements and minecraft-skills plugin paper response-patterns before finalizing an answer or generated code.
14. Use minecraft-skills plugin paper fact-surfaces to check what each plugin data surface can and cannot prove.
15. Use minecraft-skills plugin paper preflight <version> before generating plugin code.
16. Use minecraft-skills minecraft support-matrix to check the latest bundled Java/Paper aliases and whether Paper API surface facts are bundled or downloadable.
17. Use minecraft-skills minecraft support --domain paper-plugin when choosing among Paper target versions.
18. Use minecraft-skills plugin paper evidence <version> when explaining which sources and extracted files back an answer.
19. Use minecraft-skills plugin paper info to check bundled Paper support, latest Paper build metadata, and the event search API contract.
20. Use minecraft-skills plugin paper api <version> to resolve the versioned Paper API dependency, Javadocs URL, and Folia/scheduler docs.
21. Use minecraft-skills plugin paper compare-api <from> <to> to inspect versioned Paper Javadocs package additions/removals before discussing server API changes.
22. If Paper type/member surface facts are needed but not available locally, inspect minecraft-skills data manifest, then fetch the matching paper-api-surface entry before relying on it.
23. Use minecraft-skills plugin paper api-surface, minecraft-skills plugin paper types, and minecraft-skills plugin paper members to inspect Javadocs type/member names. Treat labels as API surface facts, not method behavior prose.
24. Use PaperMC documentation and API artifacts for authoritative Paper behavior.
25. Use sya-ri/spigot-event-list search API for event discovery when the user describes an event by behavior, partial name, or localized text.
26. Flag Folia-sensitive scheduling and threading assumptions instead of silently using global scheduler patterns.

CLI Commands

• minecraft-skills domain paper-plugin, minecraft-skills plugin paper info, minecraft-skills plugin paper preflight <version>, minecraft-skills plugin paper context <version>, minecraft-skills plugin paper search "<task>", minecraft-skills plugin paper recipes, minecraft-skills plugin paper recipe <id>, minecraft-skills plugin paper search-scenarios "<task>", minecraft-skills plugin paper scenarios, minecraft-skills plugin paper scenario <id>, minecraft-skills plugin paper plan <scenario-id> <version>, minecraft-skills plugin paper guardrails, minecraft-skills plugin paper diagnostics, minecraft-skills plugin paper diagnostic <id>, minecraft-skills plugin paper claim-policies, minecraft-skills plugin paper output-requirements, minecraft-skills plugin paper response-patterns, minecraft-skills plugin paper response-pattern <id>, minecraft-skills plugin paper evidence <version>, minecraft-skills plugin paper intents, minecraft-skills plugin paper intent <id>, minecraft-skills plugin paper checklist, minecraft-skills minecraft support --domain paper-plugin, minecraft-skills plugin paper fact-surfaces, minecraft-skills minecraft support-matrix, minecraft-skills data manifest, minecraft-skills data fetch paper-api-surface --version <version>, minecraft-skills plugin paper api <version>, minecraft-skills plugin paper api-index <version>, minecraft-skills plugin paper api-surface <version>, minecraft-skills plugin paper types <version>, minecraft-skills plugin paper members <version>, minecraft-skills plugin paper compare-api <from> <to>, minecraft-skills plugin paper compare-api-surface <from> <to>, minecraft-skills plugin paper events <query>, minecraft-skills minecraft compare <from> <to>

Source Priority

Use PaperMC docs and API artifacts for Paper behavior. Use Bukkit/Spigot-compatible references only when discussing compatibility or events that Paper inherits.