Playdrop

Playdrop is an AI gaming platform that helps level up vibe-coded web games. Use this skill to improve, publish, and manage your web game, app, or asset.

First steps

1. Install : npm install -g @playdrop/playdrop-cli
2. Log In first, before working on any app or game : playdrop auth login
3. Overview : playdrop getting-started
4. Initialize : existing project -> playdrop project init . ; new app -> playdrop project create app <name> --template <ref>

Use this skill when

• want to make a game prettier with Playdrop catalog assets or AI generation for images, video, 3D, music, and SFX
• want to add identity such as usernames and avatars, or persistence such as game saves
• want to reuse code references from published Playdrop games or demos to build features faster and with less risk
• want to make a game realtime multiplayer
• want to publish a game on the playdrop platform so that people can find it and play it
• want to add monetization with IAP to a game
• want to manage an existing game by reviewing comments, release history, listing updates, and new releases

Explore references

• Browse : playdrop browse ...
• Search : playdrop search <query>
• Inspect : playdrop detail <ref> --json
• Docs : playdrop documentation browse and playdrop documentation read <path>
• Inspect 2 to 3 strong references before changing art, controls, systems, or packaging.
• Command map : see references/cli-map.md
• See references/discovery.md
• See references/audio.md for gameplay audio guidance and Safari-safe SFX patterns.
• See references/performance-debugging.md for instrumentation, browser comparison, and profiling workflow.

Existing projects

• Log in before inspecting, capturing, publishing, or managing an app or game.
• If the user did not provide credentials, prefer browser login with playdrop auth login.
• Initialize in place : playdrop project init .
• Check project metadata, typically catalogue.json
• Validate : playdrop project validate .
• When the user says use $playdrop, assume registration and reference research are in scope unless they narrow the task.
• See references/existing-projects.md
• For intermittent frame drops or browser-specific bugs, see references/performance-debugging.md.

Create or remix

• New app : playdrop browse --kind app --app-type template --json then playdrop project create app <name> --template <ref>
• Remix : playdrop project create app <name> --remix <ref>
• Prefer remix when a public starter or demo is already close to the requested project.
• See references/create-and-remix.md

Porting shortcut

• Godot or engine port : inspect playdrop/app/starter-kit-racing, playdrop/app/starter-kit-3d-platformer, and playdrop/app/starter-kit-fps early.
• Use them as the default references for source freezing, scene conversion, debug hooks, hosted validation, and mobile parity unless there is a better fit.
• If you choose not to use them, say why.
• See references/godot-porting.md
• If the port includes gameplay SFX or browser-specific spikes, also read references/audio.md and references/performance-debugging.md.

Genre shortcut

• Racing, kart, or vehicle game : inspect playdrop/app/starter-kit-racing early.
• Use it as the default reference for art, controls, physics, camera, HUD, and mobile controls unless there is a better fit.
• 3D platformer or third-person character controller game : inspect playdrop/app/starter-kit-3d-platformer early.
• Use it as the default reference for movement, orbit camera, jump and landing behavior, collectibles, falling platforms, debug hooks, and mobile controls unless there is a better fit.
• First-person shooter or first-person action game : inspect playdrop/app/starter-kit-fps early.
• Use it as the default reference for pointer-lock input, viewmodel camera setup, hitscan combat, enemy combat loops, HUD, hosted validation, and landscape-only mobile touch controls unless there is a better fit.
• If you choose not to use it, say why.
• See references/racing.md
• See references/platformer-3d.md
• See references/fps.md

Services

• Playdrop services include identity, avatars, saves, realtime multiplayer, monetization, and AI generation.
• Read public docs first, then integrate only what helps the project.
• See references/services.md

Assets

• Playdrop catalog content can include code samples, 3D, images, video, music, and SFX.
• Start with playdrop browse, playdrop search, and playdrop detail.
• See references/assets-and-generation.md
• For gameplay audio implementation details and Safari-specific pitfalls, see references/audio.md.

Capture and publish

• Capture proof : playdrop project capture or playdrop project capture remote
• Validate : playdrop project validate .
• Publish : playdrop project publish .
• For listing-heavy tasks: capture gameplay first, then screenshots, hero, icon, then publish.
• See references/publish-and-listing.md

Manage live projects

• Use Playdrop creation, comment, version, and publish tools to manage releases and community activity.
• Use this when reviewing comments, preparing metadata updates, or shipping a new release.
• If you hit a bug, feature gap, or improvement idea while working, send it with playdrop feedback send.
• See references/live-ops.md

Rules

• Prefer public docs and stable CLI commands over undocumented workflows.
• If docs browsing fails, continue with playdrop help, playdrop getting-started, playdrop browse, and playdrop detail.
• Do not rely on unpublished docs, local repo paths, or non-public workflows.
• Log in before starting app or game work.
• If the user did not provide credentials, prefer browser login with playdrop auth login.
• For browser-based login or approval flows, wait for the CLI command to exit and verify success with playdrop auth whoami before responding.
• If you encounter a bug, feature request, or overall improvement idea, send it with playdrop feedback send.
• Use playdrop project capture or playdrop project capture remote when a screenshot, runtime log, or browser proof is needed.
• Keep guidance focused on public creator and developer workflows.