ui-ux-design
Skill do Designer UI/UX para definição de interfaces e experiência do usuário. Use quando precisar criar wireframes, design system tokens, componentes de UI, fluxos de navegação, acessibilidade, ou qualquer decisão de interface. Trigger em: "design", "UI", "UX", "interface", "wireframe", "componente visual", "layout", "responsivo", "mobile first", "acessibilidade", "design system", "protótipo", "Figma".
89
Quality
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, comprehensive trigger terms, explicit 'Use when' guidance, and clear domain boundaries. The description uses proper third-person voice and follows the pattern of good examples in the rubric.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'criar wireframes, design system tokens, componentes de UI, fluxos de navegação, acessibilidade' - these are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('definição de interfaces e experiência do usuário', 'criar wireframes, design system tokens...') AND when ('Use quando precisar...') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say, explicitly listed: 'design', 'UI', 'UX', 'interface', 'wireframe', 'componente visual', 'layout', 'responsivo', 'mobile first', 'acessibilidade', 'design system', 'protótipo', 'Figma'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on UI/UX design with distinct triggers like 'wireframe', 'Figma', 'design system', 'mobile first' that are unlikely to conflict with other skill types. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive UI/UX design skill with strong actionability through concrete tokens, specifications, and checklists. However, it suffers from verbosity by inlining large code blocks that could be referenced, and lacks explicit workflow validation steps for the design process itself. The progressive disclosure is well-handled with clear external references.
Suggestions
Move the full design-tokens.ts code block to a referenced file (e.g., docs/skill-guides/design-tokens.md) and keep only a brief example or summary inline
Add explicit validation checkpoints to the workflow, such as 'Validate accessibility with automated tools before handoff' or 'Review with stakeholder before finalizing wireframes'
Remove or significantly condense the Nielsen heuristics section - Claude knows these; a simple 'Apply Nielsen's 10 heuristics' with a link would suffice
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes useful content but is verbose in places - the full design tokens TypeScript file (60+ lines) could be referenced rather than inlined, and some sections like the Nielsen heuristics checklist explain concepts Claude already knows. | 2 / 3 |
Actionability | Provides concrete, executable guidance with full TypeScript token definitions, specific breakpoint values, component specification templates, and clear checklists. The handoff sections give specific deliverables rather than vague descriptions. | 3 / 3 |
Workflow Clarity | The skill lists responsibilities and handoff items clearly, but lacks explicit validation checkpoints or feedback loops. There's no clear sequence for the design process itself - when to validate accessibility, when to check with stakeholders, or how to iterate on feedback. | 2 / 3 |
Progressive Disclosure | Well-structured with clear references to external files (GLOBAL.md, policies/, docs/skill-guides/) for detailed content. The main skill provides an overview with one-level-deep references that are clearly signaled. | 3 / 3 |
Total | 10 / 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
- felvieira/claude-skills-fv
- Commit
524725e
- 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.