ui-ux-expert
Expert UI/UX designer specializing in user-centered design, accessibility (WCAG 2.2), design systems, and responsive interfaces. Use when designing web/mobile applications, implementing accessible interfaces, creating design systems, or conducting usability testing.
68
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/ui-ux-expert/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description has strong completeness with an explicit 'Use when...' clause and good trigger term coverage including specific standards like WCAG 2.2. However, it uses first-person role framing ('Expert UI/UX designer') instead of action-oriented third person, and the capabilities listed are somewhat broad rather than concrete specific actions.
Suggestions
Rewrite to use third-person action verbs instead of role-based framing (e.g., 'Creates wireframes, designs accessible interfaces, builds design systems' instead of 'Expert UI/UX designer specializing in...')
Add more specific concrete actions like 'create wireframes', 'audit color contrast', 'design component libraries', 'evaluate navigation patterns' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (UI/UX design) and mentions areas like accessibility, design systems, and responsive interfaces, but uses role-based language ('Expert UI/UX designer') rather than listing concrete actions. The actions mentioned (designing, implementing, creating, conducting) are somewhat generic. | 2 / 3 |
Completeness | Clearly answers both what (UI/UX design, accessibility, design systems, responsive interfaces) and when with explicit 'Use when...' clause covering designing applications, implementing accessible interfaces, creating design systems, and conducting usability testing. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'UI/UX', 'accessibility', 'WCAG 2.2', 'design systems', 'responsive', 'web/mobile applications', 'usability testing'. These are terms users would naturally use when seeking design help. | 3 / 3 |
Distinctiveness Conflict Risk | While it specifies UI/UX and accessibility focus, terms like 'web/mobile applications' and 'design systems' could overlap with frontend development skills or general design skills. The WCAG 2.2 reference adds some distinctiveness. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, executable guidance with excellent code examples and comprehensive coverage of UI/UX topics. However, it severely violates token efficiency by explaining concepts Claude already knows (WCAG principles, semantic HTML basics, what design systems are) and includes far too much inline content that should be in referenced files. The skill would be significantly more effective at 20-30% of its current length.
Suggestions
Remove explanatory content about concepts Claude already knows (e.g., 'PDF files are a common file format', WCAG principle definitions, what semantic HTML is) - keep only the specific implementation patterns and code
Move Sections 4-8 (Performance Patterns, Core Responsibilities, UX Patterns, Accessibility Standards, Common Mistakes) to separate reference files and link to them from a concise overview
Consolidate the pre-implementation checklist and testing sections into a single, streamlined workflow with explicit validation checkpoints and error recovery steps
Reduce the main SKILL.md to a quick-start overview (~100-150 lines) with clear pointers to detailed reference materials
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~1000+ lines with extensive explanations of concepts Claude already knows (what WCAG is, basic HTML semantics, what design systems are). Contains redundant sections and excessive context that doesn't add actionable value. | 1 / 3 |
Actionability | Provides fully executable code examples throughout - Vue components, TypeScript tests, HTML patterns, and bash commands are all copy-paste ready with specific implementations. | 3 / 3 |
Workflow Clarity | The TDD workflow in Section 3 has clear steps with validation, but many other sections lack explicit sequencing. The pre-implementation checklist is comprehensive but presented as a wall of checkboxes without clear feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | References external files (references/design-patterns.md, references/accessibility-guide.md) appropriately, but the main document is monolithic with massive inline content that should be split into separate reference files. Too much detail in the primary skill file. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1567 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 12 / 16 Passed | |
- Repository
- martinholovsky/claude-skills-generator
- Commit
1086ef2
- Reviewed
Table of Contents
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.