Build fast, polished 2D browser games using Phaser 3's scene-based architecture and physics systems.
Works with
Scene-first architecture organizes games into distinct lifecycle phases (Boot, Menu, Game, Pause, GameOver) with clean state management across transitions
Supports Arcade physics for speed and simplicity, Matter physics for realistic simulations, and physics-free scenes for menus and overlays
Covers sprites, animations, tilemaps (Tiled integration), input handling (keyboard, pointer,
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionphaser-gamedevExecute the skills CLI command in your project's root directory to begin installation:
Fetches phaser-gamedev from chongdashu/phaserjs-tinyswords and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate phaser-gamedev. Access via /phaser-gamedev in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
5
total installs
5
this week
33
GitHub stars
0
upvotes
Run in your terminal
5
installs
5
this week
33
stars
Build fast, polished 2D browser games using Phaser 3's scene-based architecture and physics systems.
Games are not static UIs—they are dynamic systems where entities interact, state evolves, and player input drives everything. Before writing code, think architecturally.
Before building, ask:
Core principles:
Every Phaser game starts with a configuration object.
const config = {
type: Phaser.AUTO, // WebGL with Canvas fallback
width: 800,
height: 600,
scene: [BootScene, GameScene]
};
const game = new Phaser.Game(config);
const config = {
type: Phaser.AUTO,
width: 800,
height: 600,
parent: 'game-container', // DOM element ID
backgroundColor: '#2d2d2d',
scale: {
mode: Phaser.Scale.FIT,
autoCenter: Phaser.Scale.CENTER_BOTH
},
physics: {
default: 'arcade',
arcade: {
gravity: { y: 300 },
debug: false // Enable during development
}
},
scene: [BootScene, MenuScene, GameScene, GameOverScene]
};
| System | Use When |
|---|---|
| Arcade | Platformers, shooters, most 2D games. Fast, simple AABB collisions |
| Matter | Physics puzzles, ragdolls, realistic collisions. Slower, more accurate |
| None | Menu scenes, visual novels, card games |
Scenes are the fundamental organizational unit. Each scene has a lifecycle.
class GameScene extends Phaser.Scene {
constructor() {
super('GameScene'); // Scene key for reference
}
init(data) {
// Called first. Receive data from previous scene
this.level = data.level || 1;
}
preload() {
// Load assets. Runs before create()
this.load.image('player', 'assets/player.png');
this.load.spritesheet('enemy', 'assets/enemy.png', {
frameWidth: 32, frameHeight: 32
});
}
create() {
// Set up game objects, physics, input
this.player = this.physics.add.sprite(100, 100, 'player');
this.cursors = this.input.keyboard.createCursorKeys();
}
update(time, delta) {
// Game loop. Called every frame
// delta = milliseconds since last frame
this.player.x += this.speed * (delta / 1000);
}
}
// Start a new scene (stops current)
this.scene.start('GameOverScene', { score: this.score });
// Launch scene in parallel (both run)
this.scene.launch('UIScene');
// Pause/resume scenes
this.scene.pause('GameScene');
this.scene.resume('GameScene');
// Stop a scene
this.scene.stop('UIScene');
scenes/
├── BootScene.js # Asset loading, progress bar
├── MenuScene.js # Title screen, options
├── GameScene.js # Main gameplay
├── UIScene.js # HUD overlay (launched parallel)
├── PauseScene.js # Pause menu overlay
└── GameOverScene.js # End screen, restart option
Everything visible in Phaser is a Game Object.
// Images (static)
this.add.image(400, 300, 'background');
// Sprites (can animate, physics-enabled)
const player = this.add.sprite(100, 100, 'player');
// Text
const score = this.add.text(16, 16, 'Score: 0', {
fontSize: '32px',
fill: '#fff'
});
// Graphics (draw shapes)
const graphics = this.add.graphics();
graphics.fillStyle(0xff0000);
graphics.fillRect(100, 100, 50, 50);
✓Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
✓Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
grill-me
706mattpocock/skills
Productivitysame categorypremortem
218parcadei/continuous-claude-v3
Productivitysame categorydeslop
164cursor/plugins
Productivitysame categorytravel-planner
145ailabs-393/ai-labs-claude-skills
Productivitysame categoryframer-motion
141pproenca/dot-skills
Productivitysame categorynutritional-specialist
141ailabs-393/ai-labs-claude-skills
Productivitysame categoryReviews
4.7★★★★★56 reviews- XXiao Gupta★★★★★Dec 20, 2024
phaser-gamedev reduced setup friction for our internal harness; good balance of opinion and flexibility.
- AAisha Singh★★★★★Dec 16, 2024
We added phaser-gamedev from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- OOmar Srinivasan★★★★★Dec 8, 2024
phaser-gamedev is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- SShikha Mishra★★★★★Dec 4, 2024
phaser-gamedev has been reliable in day-to-day use. Documentation quality is above average for community skills.
- MMaya Yang★★★★★Nov 27, 2024
Useful defaults in phaser-gamedev — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- YYash Thakker★★★★★Nov 23, 2024
Keeps context tight: phaser-gamedev is the kind of skill you can hand to a new teammate without a long onboarding doc.
- XXiao Patel★★★★★Nov 11, 2024
Registry listing for phaser-gamedev matched our evaluation — installs cleanly and behaves as described in the markdown.
- AAma Malhotra★★★★★Nov 7, 2024
phaser-gamedev fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- NNoah Park★★★★★Oct 26, 2024
phaser-gamedev has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ZZaid Kapoor★★★★★Oct 18, 2024
Registry listing for phaser-gamedev matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 56
1 / 6Discussion
Comments — not star reviews- No comments yet — start the thread.