ui-advice
Provides UI/UX design pattern advice and generates text wireframes
56
45%
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 ./.claude/skills/ui-advice/SKILL.mdQuality
Discovery
32%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 identifies a reasonable niche (UI/UX design advice and text wireframes) but is too brief and lacks explicit trigger guidance. It would benefit from listing more specific capabilities and adding a 'Use when...' clause to help Claude distinguish this skill from general design or frontend development skills.
Suggestions
Add a 'Use when...' clause with trigger terms like 'wireframe', 'mockup', 'UI layout', 'design pattern', 'user interface design', 'screen layout'.
List more specific concrete actions, e.g., 'Recommends navigation patterns, form layouts, responsive design approaches, and generates ASCII/text-based wireframes for screens and components'.
Include common user phrasing variations such as 'prototype', 'page layout', 'UX flow', 'component design' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (UI/UX design) and two actions ('provides design pattern advice' and 'generates text wireframes'), but these are not highly specific or comprehensive — it doesn't elaborate on what kinds of patterns, what format wireframes take, or other concrete capabilities. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'what' is also only moderately detailed, this scores at 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'UI/UX', 'design pattern', and 'wireframes' which users might naturally say, but misses common variations like 'mockup', 'layout', 'prototype', 'user interface', 'user experience', or 'screen design'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'UI/UX design patterns' and 'text wireframes' is somewhat distinctive, but could overlap with general design advice skills, frontend development skills, or prototyping tools without clearer scoping. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a moderately well-structured advisory skill that provides a clear output format and wireframe conventions. Its main weaknesses are the lack of concrete decision-making heuristics for choosing design patterns and some unnecessary meta-description of what the skill does. The example output is the strongest element, giving Claude a clear template to follow.
Suggestions
Replace the generic guidelines ('consider usability, accessibility') with specific heuristics or decision criteria, e.g., 'For data-heavy UIs prefer table layouts; for browsing/discovery prefer card grids; for form-heavy flows prefer stepped wizards'.
Remove the 'What This Skill Provides' and 'Usage' sections — they describe the skill rather than instruct Claude, wasting tokens on meta-information Claude can infer from the example output.
Add a brief decision workflow: e.g., 'Ask clarifying questions about content type, user goals, and device targets before suggesting patterns' to make the process more actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary sections like 'What This Skill Provides' which essentially describes what Claude should do rather than how. The 'Usage' section at the bottom is also redundant. However, the wireframe rules and example output are reasonably lean. | 2 / 3 |
Actionability | Provides a concrete example output format and wireframe conventions, which is helpful. However, the guidance is more about what to produce than how to produce it — there are no specific decision frameworks, no concrete heuristics for choosing patterns, and the guidelines are fairly generic (e.g., 'consider usability, accessibility'). The example output is a template rather than executable guidance. | 2 / 3 |
Workflow Clarity | The numbered list in 'What This Skill Provides' implies a sequence (suggest patterns → explain → wireframe → recommend), but there's no explicit workflow with steps to follow. For a non-destructive advisory skill this is less critical, but the process could be more clearly sequenced with decision points (e.g., when to suggest fewer patterns, how to narrow recommendations). | 2 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into clear sections (guidelines, wireframe rules, example output). The structure is logical and easy to navigate without requiring additional files. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- sc30gsw/claude-code-customes
- Commit
7aff694
- 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.