phaser-coder

Name: phaser-coder
Author: Yakoub-ai

62installs0forks

How to install phaser-coder?

yakoub-ai/phaser4-gamedev/phaser-coder

$npx -y skills add Yakoub-ai/phaser4-gamedev --skill phaser-coder

Installs into the current project.

Summary

This skill should be used when the user asks to implement Phaser 4 game code, create or edit scenes, add players, enemies, scoring, collectibles, movement, shooting, animations, input, physics behavior, game objects, or complete gameplay features in TypeScript.

Files · 1

View on GitHub

SKILL.md

1	# Phaser 4 Coder
2
3	Use this skill for TypeScript-first Phaser 4 implementation work.
4
5	## Workflow
6
7	1. Read existing code before editing. Inspect `src/main.ts`, scene files, related objects/managers, shared constants, and asset keys.
8	2. Match existing naming, folder structure, scene key conventions, and state management patterns.
9	3. Use Phaser 4 APIs only. Avoid removed Phaser 3 APIs such as `Phaser.Geom.Point`, `Phaser.Math.PI2`, `Phaser.Structs`, and deprecated texture generation patterns.
10	4. Prefer typed constants/enums for scene keys, registry keys, event names, asset keys, and animation keys.
11	5. Write complete runnable code. Avoid placeholder TODOs unless the user explicitly asks for a scaffold.
12	6. After non-trivial edits, run `npx tsc --noEmit` when the project has TypeScript configured.
13
14	## Implementation Defaults
15
16	- Use class-based scenes extending `Phaser.Scene`.
17	- Use Arcade Physics for typical platformer/top-down/shooter mechanics unless Matter.js is clearly required.
18	- Use object pooling for bullets, enemies, particles, and frequent temporary objects.
19	- Put shared types under `src/types/` and reusable game objects under `src/objects/` or the existing local equivalent.
20	- Gate debug affordances behind development mode where possible.
21	- Keep Vite and Phaser setup compatible with browser runtime and strict TypeScript.
22
23	## Full Guidance
24
25	For the complete coding playbook, read `references/agent-guidance.md`. It is copied from the Claude subagent definition but should be applied as a portable skill; ignore Claude-only fields such as `model`, `color`, and `tools`.

People who liked this also viewed

6 picks

Type

phaser-coder

62installs0forks

View on GitHub

How to install phaser-coder?

yakoub-ai/phaser4-gamedev/phaser-coder

$npx -y skills add Yakoub-ai/phaser4-gamedev --skill phaser-coder

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Phaser 4 Coder
2
3	Use this skill for TypeScript-first Phaser 4 implementation work.
4
5	## Workflow
6
7	1. Read existing code before editing. Inspect `src/main.ts`, scene files, related objects/managers, shared constants, and asset keys.
8	2. Match existing naming, folder structure, scene key conventions, and state management patterns.
9	3. Use Phaser 4 APIs only. Avoid removed Phaser 3 APIs such as `Phaser.Geom.Point`, `Phaser.Math.PI2`, `Phaser.Structs`, and deprecated texture generation patterns.
10	4. Prefer typed constants/enums for scene keys, registry keys, event names, asset keys, and animation keys.
11	5. Write complete runnable code. Avoid placeholder TODOs unless the user explicitly asks for a scaffold.
12	6. After non-trivial edits, run `npx tsc --noEmit` when the project has TypeScript configured.
13
14	## Implementation Defaults
15
16	- Use class-based scenes extending `Phaser.Scene`.
17	- Use Arcade Physics for typical platformer/top-down/shooter mechanics unless Matter.js is clearly required.
18	- Use object pooling for bullets, enemies, particles, and frequent temporary objects.
19	- Put shared types under `src/types/` and reusable game objects under `src/objects/` or the existing local equivalent.
20	- Gate debug affordances behind development mode where possible.
21	- Keep Vite and Phaser setup compatible with browser runtime and strict TypeScript.
22
23	## Full Guidance
24
25	For the complete coding playbook, read `references/agent-guidance.md`. It is copied from the Claude subagent definition but should be applied as a portable skill; ignore Claude-only fields such as `model`, `color`, and `tools`.

People who liked this also viewed

6 picks

Type