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-routing when 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.

Install the Plugin

Codex

Use this exact local Codex setup:

Copy the plugin repo into:

text example

~/.codex/plugins/playdrop

Create or update:

text example

~/.agents/plugins/marketplace.json

with:

json example

{
  "name": "local-plugins",
  "interface": {
    "displayName": "Local Plugins"
  },
  "plugins": [
    {
      "name": "playdrop",
      "source": {
        "source": "local",
        "path": "./.codex/plugins/playdrop"
      },
      "policy": {
        "installation": "AVAILABLE",
        "authentication": "ON_INSTALL"
      },
      "category": "Coding"
    }
  ]
}

Restart Codex so it reloads the personal marketplace.
Open Plugins > Local Plugins, then install playdrop from local-plugins.
Start a new thread and ask Codex to use playdrop or one of its bundled skills.

Optional advanced shortcut for personal setups:

toml example

[plugins."playdrop@local-plugins"]
enabled = true

Add that entry to ~/.codex/config.toml if you want Codex to keep the plugin enabled after it has been installed. Treat it as a local shortcut for your own machine, not the primary install path. If PlayDrop does not appear, use the restart plus Plugins > Local Plugins flow above.

Claude Code

Either run these commands in Claude CLI directly, or tell the Claude app to run them with Claude CLI.

bash example

/plugin marketplace add playdrop-ai/playdrop-plugin
/plugin install playdrop@playdrop

/plugin is not available inside the Claude Code app at the moment.

Cursor

Copy this prompt into Cursor to register the plugin:

text example

Install the PlayDrop Cursor Plugin from https://github.com/playdrop-ai/playdrop-plugin in ~/.cursor/plugins/local/
Source: https://cursor.com/docs/plugins#creating-plugins

Recommended workflow

After the plugin is installed, pair it with the CLI:

bash example

npm install -g @playdrop/playdrop-cli
playdrop auth login
playdrop auth whoami
playdrop documentation browse

After 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