Playdrop Plugin
The public playdrop plugin is the preferred way to bring Playdrop into an AI coding workflow.
It replaces the old single-skill model with one plugin that contains many specialist skills. That gives better routing, smaller context per task, and stronger results across Codex, Claude Code, and Cursor.
Canonical public source: playdrop-plugin.
Legacy compatibility surface: playdrop-skills and the legacy skill page.
Why the plugin is preferred
- one public plugin with many focused creator workflows
- better auto-routing through
task-routingwhen the right workflow is not obvious - better support for Codex, Claude Code, and Cursor
- shared references and assets without collapsing everything into one umbrella skill
Specialist skills inside the plugin
- planning and scope:
task-routing,game-planning,scope-control,gameplay-mockups - building and iteration:
asset-discovery,project-updates,dev-testing,game-improvement,gameplay-review - publishing and growth:
store-listing,comment-monitoring,game-marketing - platform integration and support:
service-integration,engine-porting,creator-support
If you are not sure which one to use, start with task-routing and let the plugin route the work.
Recommended workflow
Install the Playdrop plugin using your AI tool's plugin install flow, then pair it with the CLI:
bash example
npm install -g @playdrop/playdrop-cli
playdrop auth login
playdrop auth whoami
playdrop documentation browseAfter that, move into the right creator workflow:
bash example
playdrop project init .
playdrop project create app my-first-app --template playdrop/template/typescript_template
playdrop project dev my-first-app
playdrop project validate .Legacy compatibility
The old umbrella playdrop skill is still supported for legacy skill-first environments and skills.sh installs, but it is no longer the preferred public setup.
Use the legacy skill only when your environment cannot install the plugin yet:
bash example
npx skills add https://github.com/playdrop-ai/playdrop-skills --skill playdrop