oh-my-ai/uiux
Self-contained UI/UX design intelligence: priority ladder, design reference (style, color, type, landing, charts, perf), polish checks, file-first design-system artifacts; deep defaults on React, Next.js, Tailwind, RN, Flutter.
94
94%
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 an exceptionally well-crafted skill description that excels across all dimensions. It provides comprehensive trigger terms covering both high-level concepts (landing pages, dashboards) and specific components (modals, navbars), clearly delineates when to use and when not to use the skill, and lists concrete capabilities with specific output artifacts. The description is thorough without being padded, and uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists numerous specific concrete actions: creating design-system token files, generating responsive Tailwind layouts, scaffolding page-level component hierarchies, reviewing/fixing UI accessibility, implementing React Native safe-area screens, configuring Flutter ThemeData, and producing specific output artifacts (MASTER.md, page overrides, tokens, component specs). | 3 / 3 |
Completeness | Clearly answers both 'what' (capabilities paragraph listing specific actions and outputs) and 'when' (explicit 'Use when...' clause with detailed trigger scenarios). Also includes a 'Do NOT use for' clause which further clarifies boundaries. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'UI components', 'modals', 'forms', 'tables', 'charts', 'navbars', 'sidebars', 'cards', 'landing pages', 'dashboards', 'admin panels', 'SaaS', 'mobile app screens', 'dark mode', 'responsive breakpoints', 'design system', 'accessibility', 'a11y', 'WCAG', plus framework names like React, Next.js, Tailwind CSS, React Native, Flutter. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around UI/UX design across specific frontend frameworks, with distinct triggers like design-system tokens, MASTER.md artifacts, and specific component types. The 'Do NOT use for' clause further reduces conflict risk by explicitly excluding backend-only work. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, high-quality skill that provides clear multi-phase workflows, executable code examples across multiple stacks, and excellent progressive disclosure through companion rule files. Its main weakness is minor verbosity — the integrated example and anti-patterns section, while useful, add length that partially overlaps with the process phases and non-negotiables. Overall it is a strong skill that would effectively guide Claude in UI/UX implementation tasks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some verbosity — e.g., the integrated example section restates what the process phases already cover, and some non-negotiables could be tighter. However, it mostly avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | Provides fully executable code examples for React/Tailwind, React Native, and references Flutter ThemeData. The process phases give concrete steps (inspect package.json, create specific files, run checklists), and the integrated example demonstrates a real end-to-end scenario with specific implementation details. | 3 / 3 |
Workflow Clarity | The 5-phase process is clearly sequenced (classify → load references → plan artifacts → implement → pre-delivery pass), with an explicit validation checkpoint in Phase 5 referencing specific checklists. The integrated example demonstrates the workflow applied to a concrete scenario, reinforcing the sequence. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure — the SKILL.md serves as a clear overview with well-signaled one-level-deep references to companion rule files (stacks.md, ux-priority.md, design-reference.md, professional-ui.md, deliverables.md). Content is appropriately split between the overview and detailed rule files. | 3 / 3 |
Total | 11 / 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.
Reviewed
Table of Contents