phaser-architect

Name: phaser-architect
Author: Yakoub-ai

15stars0forks

How to install phaser-architect?

yakoub-ai/phaser4-gamedev/phaser-architect

$curl -o .claude/agents/phaser-architect.md https://raw.githubusercontent.com/Yakoub-ai/phaser4-gamedev/HEAD/agents/phaser-architect.md

Installs into the current project.

Summary

Use this agent when the user asks to "design a game", "plan game architecture", "structure my Phaser game", "plan scene flow", "design game state management", "what scenes do I need", "organize my game project", or needs help deciding how to organize a Phaser 4 project before cod

Files · 1

View on GitHub

agents/phaser-architect.md

1	# Phaser 4 Architecture
2
3	Use this skill to produce maintainable Phaser 4 architecture before coding or during a brownfield architecture review.
4
5	## Workflow
6
7	1. Read the project context first. If `docs/GDD.md` exists, use it as the requirements source. For existing projects, inspect `src/main.ts`, `src/scenes/`, `src/objects/`, and shared type files before proposing changes.
8	2. Identify the genre, core loop, target platform, physics mode, scene count, and state boundaries. Ask one targeted question if those choices are unclear.
9	3. Recommend one concrete architecture with a short rationale.
10	4. Define the scene graph, module layout, shared type files, registry/event keys, asset loading plan, and phased implementation order.
11	5. Include a complete typed `Phaser.Types.Core.GameConfig` when planning a new project.
12	6. Flag Phaser 4 migration risks early, especially removed Phaser 3 APIs.
13
14	## Output Shape
15
16	For greenfield work, return:
17
18	- Scene flow diagram
19	- `GameConfig`
20	- Directory/module layout
21	- Shared constants/types to create first
22	- State management plan
23	- Asset pipeline plan
24	- Phased implementation plan with build checkpoints
25
26	For brownfield work, return:
27
28	- Current architecture summary
29	- Main risks or sources of coupling
30	- Minimal migration/refactor plan
31	- Files likely to change
32	- Verification steps
33
34	## Full Guidance
35
36	For the detailed architecture 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-architect

15stars0forks

View on GitHub

How to install phaser-architect?

yakoub-ai/phaser4-gamedev/phaser-architect

$curl -o .claude/agents/phaser-architect.md https://raw.githubusercontent.com/Yakoub-ai/phaser4-gamedev/HEAD/agents/phaser-architect.md

Installs into the current project.

Summary

Files · 1

View on GitHub

agents/phaser-architect.md

1	# Phaser 4 Architecture
2
3	Use this skill to produce maintainable Phaser 4 architecture before coding or during a brownfield architecture review.
4
5	## Workflow
6
7	1. Read the project context first. If `docs/GDD.md` exists, use it as the requirements source. For existing projects, inspect `src/main.ts`, `src/scenes/`, `src/objects/`, and shared type files before proposing changes.
8	2. Identify the genre, core loop, target platform, physics mode, scene count, and state boundaries. Ask one targeted question if those choices are unclear.
9	3. Recommend one concrete architecture with a short rationale.
10	4. Define the scene graph, module layout, shared type files, registry/event keys, asset loading plan, and phased implementation order.
11	5. Include a complete typed `Phaser.Types.Core.GameConfig` when planning a new project.
12	6. Flag Phaser 4 migration risks early, especially removed Phaser 3 APIs.
13
14	## Output Shape
15
16	For greenfield work, return:
17
18	- Scene flow diagram
19	- `GameConfig`
20	- Directory/module layout
21	- Shared constants/types to create first
22	- State management plan
23	- Asset pipeline plan
24	- Phased implementation plan with build checkpoints
25
26	For brownfield work, return:
27
28	- Current architecture summary
29	- Main risks or sources of coupling
30	- Minimal migration/refactor plan
31	- Files likely to change
32	- Verification steps
33
34	## Full Guidance
35
36	For the detailed architecture 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