design

Autonomous design partner for frontend interfaces. Scans the project, writes audit reports, reviews the findings, then fixes the interface itself and verifies the result, across every visual discipline: color, typography, layout, motion, interaction, accessibility, responsive behavior, voice, and surface.

1.77x

Quality

72%

Does it follow best practices?

Impact

78%

1.77x

Average score across 1 eval scenario

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./SKILL.md

Quality

Content

73%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, highly actionable skill body with an excellent validated workflow and clean reference navigation; its main weakness is length and repetition across several overlapping process sections.

Suggestions

Consolidate the overlapping process sections (Brief Sufficiency, When in doubt, How to Actually Work, Truthful Completion, Scope Discipline) to reduce repetition and tighten token use.

Trim or remove the generic "Quality control: Perfect execution principles" block, whose bullets (Understand the current state, Define the goal, Plan systematically) state what Claude already knows.

Consider moving the large inline Design Philosophy heuristics into a dedicated reference file to keep SKILL.md a leaner overview, raising the progressive-disclosure score.

Dimension	Reasoning	Score
Conciseness	Mostly dense and operational, but ~500 lines with overlapping sections (Brief Sufficiency, When in doubt, How to Actually Work, Truthful Completion) and a generic "Quality control: Perfect execution principles" block that could be trimmed.	3 / 5
Actionability	Concrete, actionable guidance throughout—specific file paths, tool verbs, file extensions to detect, and quantified heuristics (60-76ch measure, 44x44px targets, 2-3px focus rings)—with only minor gaps for an instruction-oriented skill.	4 / 5
Workflow Clarity	The autonomous sweep is a clearly numbered Scan/Report/Review/Work/Final-response sequence with explicit validation ("Verify before continuing"), feedback loops (fix-and-reverify, stale-audit rerun), and stop conditions.	5 / 5
Progressive Disclosure	Well-signaled one-level-deep references (Tools table plus a discipline-reference list, all 27 linked files verified present) with a clean overview, though the inline Design Philosophy block is large enough to be a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

71%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, specific description of what the skill does across many design disciplines, but it lacks an explicit "Use when..." trigger clause, which caps completeness and limits trigger-term quality.

Suggestions

Add an explicit "Use when..." clause naming natural trigger phrases (e.g., redesigning a frontend, fixing accessibility, improving typography/color/layout) to satisfy the completeness anchor.

Include concrete file extensions or artifact types (.html, .css, .tsx, .vue, landing pages, dashboards) to lift trigger-term coverage toward comprehensive.

Tighten the discipline list or pair it with the trigger phrasing so the description signals when Claude should pick this skill over a general coding skill.

Dimension	Reasoning	Score
Specificity	Lists five concrete actions ("Scans the project, writes audit reports, reviews the findings, then fixes the interface itself and verifies the result") plus nine named disciplines, matching the comprehensive-coverage anchor.	5 / 5
Completeness	The "what" is clear and detailed, but there is no "Use when..." clause or equivalent trigger guidance, so per the rubric cap completeness cannot exceed 3.	3 / 5
Trigger Term Quality	Good natural keyword coverage (design, frontend interfaces, color, typography, layout, motion, accessibility, responsive) but omits file extensions (.html/.css/.tsx) and explicit user phrasings, so it sits below the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	The autonomous scan-report-review-fix-verify niche for frontend interfaces is mostly distinct, with only minor overlap risk against other UI/design skills.	4 / 5
	Total	16 / 20 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: administrakt0r/commandcode-design-skills
Path: SKILL.md
Commit: 020233c

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