phaser-best-practices

Builds and refactors Phaser 3 browser games. Use for creating a new Phaser project, adding scenes, entities, physics, UI, tilemaps, animations, input, audio, camera, or for fixing Phaser-specific bugs and performance problems.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, mostly lean framework skill with concrete defaults and clean progressive disclosure into seven real reference files. Workflows are sequenced with validation emphasis, though an explicit validate-retry feedback loop would lift workflow clarity further.

Suggestions

Add an explicit validate->fix->retry feedback loop to the debugging workflow (e.g. 'run repro, if still failing, re-isolate and re-patch') to push workflow_clarity toward 5.

Include one small runnable code snippet (e.g. a minimal game config) in the examples so the skill has copy-paste-ready, executable guidance.

Trim the three worked examples or fold the redundant default lists into the 'Default technical choices' section to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — defaults, rules, and traps are stated as terse imperatives without explaining what Phaser is. A few sections (e.g. the worked examples) could be trimmed slightly, keeping it just short of a 5.	4 / 5
Actionability	Concrete, specific guidance throughout — named APIs ('Arcade Physics', 'pixelArt', 'NineSlice / ThreeSlice', 'FIT' scaling) and explicit defaults rather than abstractions. It lacks copy-paste code blocks, but as an instruction/framework skill the named-API specificity is actionable; minor gaps remain.	4 / 5
Workflow Clarity	Three sequenced workflows (new project, feature refactor, debugging) with numbered steps and repeated emphasis on validation ('validation steps the user can run immediately', 'Add cleanup and validation steps', 'Provide a quick repro'). Validation is present but not framed as an explicit validate->fix->retry loop, capping it just below 5.	4 / 5
Progressive Disclosure	A clear Reference map points to seven one-level-deep reference files, all of which exist in references/, organized by topic and explicitly signaled; the body explicitly instructs keeping SKILL.md-level advice concise and moving detail into references.	5 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that is specific, third-person, and explicitly couples capabilities with a 'Use for' trigger clause. It is highly distinct and unlikely to fire for unrelated skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Builds and refactors', 'creating a new Phaser project', 'adding scenes, entities, physics, UI, tilemaps, animations, input, audio, camera', 'fixing Phaser-specific bugs and performance problems' — comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' ('Builds and refactors Phaser 3 browser games') and 'when' with a concrete 'Use for ...' trigger clause enumerating the triggering tasks.	5 / 5
Trigger Term Quality	Strong natural keyword coverage ('Phaser project', 'scenes', 'physics', 'tilemaps', 'animations', 'audio', 'camera', 'bugs', 'performance') that users would naturally say; a few common synonyms (e.g. 'sprite', 'game loop', 'collider') are absent.	4 / 5
Distinctiveness Conflict Risk	Clear niche scoped to 'Phaser 3 browser games' with engine-specific triggers, making conflict with other skills minimal.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: onmax/nuxt-skills
Path: skills/phaser-best-practices/SKILL.md
Commit: 50878f5

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.