ui-ux-designer

Create interface designs, wireframes, and design systems. Masters user research, accessibility standards, and modern design tools. Specializes in design tokens, component libraries, and inclusive design. Use PROACTIVELY for design systems, user flows, or interface optimization.

Quality

48%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/ui-ux-designer/SKILL.md

Quality

Content

21%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.

The body is a generic, templated capability catalog that restates UI/UX domain knowledge without providing executable guidance, concrete workflows, or progressive disclosure via reference files. It reads as a padded knowledge dump rather than actionable skill instructions.

Suggestions

Replace the generic 'Instructions' and capability bullet lists with concrete, executable guidance — e.g., specific Figma/Style Dictionary commands, token-naming conventions, or accessibility-check commands Claude can actually run.

Move the long capability and knowledge-base enumerations into reference files (e.g., references/capabilities.md, references/accessibility-checklist.md) and link to them from a lean SKILL.md overview, improving both conciseness and progressive disclosure.

Turn the 'Response Approach' into a real sequenced workflow with explicit validation checkpoints (e.g., 'run accessibility audit -> fix findings -> re-audit -> only then hand off'), especially for destructive/batch operations like design-token migrations.

Dimension	Reasoning	Score
Conciseness	The ~200-line body is noticeably verbose, enumerating UI/UX domain knowledge Claude already knows (e.g., 'Atomic design methodology with token-based architecture', 'WCAG 2.1/2.2 AA and AAA compliance implementation') across many padded bulleted sections rather than adding net-new guidance.	2 / 5
Actionability	It describes capabilities rather than instructing: there is no executable code, no concrete commands, and the 'Instructions' are generic ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes'), matching the 'entirely vague or abstract; only describes rather than instructs' anchor.	1 / 5
Workflow Clarity	The 'Response Approach' gives a rough 8-step sequence (Research user needs, Design systematically, Prioritize accessibility...), but steps are poorly defined high-level phases with no validation checkpoints or feedback loops for risky operations.	2 / 5
Progressive Disclosure	Section headers (Capabilities, Behavioral Traits, Knowledge Base, Response Approach) provide some structure, but the large capability/knowledge bullet lists are inlined in SKILL.md with no references to separate files, and the skill far exceeds the 50-line simple-skill exception.	3 / 5
	Total	8 / 20 Passed

Description

75%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.

The description is well-constructed: third-person voice, concrete actions, and an explicit 'Use PROACTIVELY' trigger clause covering both what and when. It is slightly held back by terse trigger phrasing and a few missing common synonyms (UI/UX, Figma, prototyping).

Dimension	Reasoning	Score
Specificity	Lists several concrete actions such as 'Create interface designs, wireframes, and design systems' and names specific domains (design tokens, component libraries, inclusive design), though 'Masters...' and 'Specializes...' phrase expertise rather than additional actions, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers 'what' (create interface designs, wireframes, design systems) and 'when' ('Use PROACTIVELY for design systems, user flows, or interface optimization'), but the 'when' clause is terse and could be more specific with broader trigger phrases.	4 / 5
Trigger Term Quality	Includes natural terms users would say ('design systems', 'user flows', 'interface optimization', 'wireframes') with good coverage, but omits common synonyms and extensions like 'UI', 'UX', 'prototyping', 'Figma', or '.fig'.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear UI/UX design niche with distinct triggers (wireframes, design tokens, accessibility, inclusive design), with only minor overlap risk against closely related front-end or web-design skills.	4 / 5
	Total	16 / 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: rmyndharis/antigravity-skills
Path: skills/ui-ux-designer/SKILL.md
Commit: 3eff4af

Reviewed: 1 day 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.