game-ui-frontend

Design UI surfaces for browser games. Use when the user asks for HUDs, menus, overlays, responsive layouts, or visual direction that must protect the playfield.

Quality

83%

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

77%Weight 40%Scale 1-3

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

A well-organized, highly actionable standards document that avoids explaining basics Claude already knows, but it restates the playfield-protection rule across multiple sections and its external references point to files that are not present in the bundle, breaking progressive disclosure.

Suggestions

Fix or remove the dangling bundle references — ../../references/frontend-prompts.md, three-hud-layout-patterns.md, and playtest-checklist.md, plus the ../web-game-foundations/SKILL.md and ../react-three-fiber-game/SKILL.md links — none resolve in the bundle, which breaks progressive-disclosure navigation.

Consolidate the playfield-protection guidance, which currently recurs across Frontend Standards, 3D Starter Defaults, What Good Looks Like, and Anti-Patterns; state the rule once and reference it to tighten the body and lift conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and domain-specific with no basic-concept padding, but the playfield-protection rule is restated across Frontend Standards, 3D Starter Defaults, What Good Looks Like, and Anti-Patterns, so it could be tightened, matching the level-2 'mostly efficient but... could be tightened' anchor rather than the level-3 'every token earns its place' anchor.	2 / 3
Actionability	It gives concrete, quantified guidance such as 'at most one small secondary cluster', 'no more than roughly 20-25% of the viewport', and 'gate camera-control input when menus... are active', which is highly actionable for an instruction-only design skill and matches the level-3 'concrete, specific guidance' standard rather than the level-2 'incomplete / pseudocode' anchor.	3 / 3
Workflow Clarity	The numbered Frontend Standards (establish direction → theme → hierarchy → protect playfield → overlays → responsive → 3D) plus the Prompting Rules checklist give a clear ordered sequence, and there are no destructive or batch operations requiring validation checkpoints, so per the simple/guidance-skill scoring note this earns a 3 rather than being capped.	3 / 3
Progressive Disclosure	The body is well-sectioned with a dedicated References section signaling one-level-deep links, but none of the referenced paths (frontend-prompts.md, three-hud-layout-patterns.md, playtest-checklist.md, and the two sibling SKILL.md links) resolve in the bundle, so navigation is broken and it falls to the level-2 'references present but... navigation' issue rather than the level-3 'easy navigation' anchor.	2 / 3
	Total	10 / 12 Passed

Description

90%Weight 40%Scale 1-3

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: it is third-person, names a clear domain, and pairs a concrete action with an explicit 'Use when' trigger clause listing natural keywords. The only gap is specificity, which lists a single action rather than multiple concrete capabilities.

Dimension	Reasoning	Score
Specificity	"Design UI surfaces for browser games" names the domain and one concrete action, but it lists a single action rather than multiple specific concrete actions, so it matches the 'names domain and some actions, but not comprehensive' anchor rather than the level-3 'lists multiple specific concrete actions' anchor.	2 / 3
Completeness	It explicitly answers both what ("Design UI surfaces for browser games") and when ("Use when the user asks for HUDs, menus, overlays, responsive layouts...") with an explicit trigger clause, matching the level-3 'clearly answers both what AND when' anchor.	3 / 3
Trigger Term Quality	"Use when the user asks for HUDs, menus, overlays, responsive layouts" provides good coverage of natural terms a user would actually say, matching the level-3 anchor rather than the level-2 'some relevant keywords but missing common variations' anchor.	3 / 3
Distinctiveness Conflict Risk	The 'browser games' niche combined with distinctive triggers like 'HUDs, menus, overlays' and 'visual direction that must protect the playfield' carves a clear niche unlikely to fire for unrelated skills, matching the level-3 anchor.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/plugins
Path: plugins/game-studio/skills/game-ui-frontend/SKILL.md
Commit: 11c74d6

Reviewed: 17 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.