engine-porting
Engine Porting
Use this skill when the project starts outside the normal Playdrop starter flow.
Workflow
- identify the closest Playdrop starter or public reference
- use starter kits as the default migration baseline unless there is a better fit
- freeze source scope before rewriting systems
- validate core loop, controls, and performance early
- only then move to listing or publish work
Shared references
More from playdrop-ai/playdrop-skills
playdrop
Legacy compatibility Playdrop skill for public creator workflows. Use this when working from the legacy playdrop-skills repo or skills.sh distribution and you need the older umbrella Playdrop workflow instead of the preferred public plugin.
6game-marketing
Improve a Playdrop game's distribution and visibility. Use when the user asks about social sharing, GitHub SEO, discovery, boosts, or how to get a published game in front of more players.
1project-updates
Update Playdrop CLI, plugin, SDK, and project compatibility. Use when the user asks to upgrade Playdrop tooling, compare versions, read changelogs, or migrate an existing project to current public best practices.
1gameplay-mockups
Create or review gameplay mockups as literal build targets. Use when the user needs HUD framing, screen layouts, control affordances, or shipping-resolution mockups that implementation can follow directly.
1creator-support
Help a creator when they are blocked using Playdrop. Use when the user needs escalation paths, troubleshooting help, documentation navigation, feedback submission, or the simplest next step to get unstuck.
1dev-testing
Run Playdrop local development and validation workflows. Use when the user needs the dev server, local validation, test accounts, multiplayer checks, or staged creator testing before publish.
1