design-system

Guided, section-by-section GDD authoring for a single game system. Gathers context from existing docs, walks through each required section collaboratively, cross-references dependencies, and writes incrementally to file.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/design-system/SKILL.md

Quality

Content

77%

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

The content is highly actionable with an excellently sequenced and validated workflow, but it is over-long due to repeated review-mode blocks and keeps large reusable blocks inline rather than splitting them into reference files.

Suggestions

Factor the repeated solo/lean/full review-mode check into a single defined rule referenced once, instead of restating the three-case block in each section.

Move the specialist routing table, the GDD skeleton template, and the per-section completion-steering formats into separate reference files (e.g. references/routing.md, references/gdd-template.md) and link to them, reducing the main file's size.

Trim the closing 'Collaborative Protocol' section, which largely restates principles already enforced inline in each phase.

Dimension	Reasoning	Score
Conciseness	The body is substantive domain guidance with no extraneous concept explanations, but the solo/lean/full review-mode block is repeated near-verbatim across ~8 sections and the closing 'Collaborative Protocol' recap restates principles already detailed earlier, so it could be meaningfully tightened.	2 / 3
Actionability	Provides fully concrete, copy-paste-ready guidance — exact AskUserQuestion prompts with specific option text, exact file paths, exact Grep patterns, exact Edit old_string/new_string patterns, and a complete GDD template with structured completion-steering formats.	3 / 3
Workflow Clarity	A clearly sequenced five-phase flow with a defined per-section cycle and explicit validation checkpoints (registry conflict checks after each write, 5a self-check, approval gates, BLOCKED verdicts) plus feedback loops and a recovery/resume section.	3 / 3
Progressive Disclosure	The skill is a single monolithic ~870-line file with no bundle reference files; the routing table, GDD template, engine-domain table, and completion-steering formats are all inline where they could be split out, though external doc references are clearly signaled.	2 / 3
	Total	10 / 12 Passed

Description

67%

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

The description is specific, actionable, and clearly niche-specific, but it lacks an explicit 'Use when…' trigger clause and broader natural-language trigger terms, leaving the 'when to use it' only implied.

Suggestions

Add an explicit trigger clause, e.g. 'Use when designing or authoring a single game system's GDD, or retrofitting an existing GDD to fill missing sections.'

Broaden trigger terms with natural phrasings users would say — 'design a game system', 'write a game design document', 'fill in a GDD' — alongside 'GDD authoring'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Gathers context from existing docs', 'walks through each required section collaboratively', 'cross-references dependencies', 'writes incrementally to file' — matching the multiple-specific-actions anchor.	3 / 3
Completeness	The 'what' is clearly and comprehensively stated, but there is no 'Use when…' or equivalent explicit trigger clause, so the 'when' is only implied and completeness is capped at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	'GDD authoring' and 'game system' are natural terms, but capability phrases like 'writes incrementally to file' are not user-spoken triggers and common variations such as 'design' or 'write a GDD' are missing.	2 / 3
Distinctiveness Conflict Risk	'GDD authoring for a single game system' is a narrow, well-defined niche with distinct triggers, making it unlikely to fire for an unrelated skill.	3 / 3
	Total	10 / 12 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (872 lines); consider splitting into references/ and linking	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: Donchitos/Claude-Code-Game-Studios
Path: .claude/skills/design-system/SKILL.md
Commit: 984023d

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