CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-domain-uiux

UI/UX design systems specialist covering accessibility, icons, theming, design tokens, and user experience patterns. Use when working on design systems, WCAG compliance, ARIA patterns, or dark mode theming.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.moai/archive/skills/v3.0/moai-domain-uiux/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 well-organized overview with sequenced workflows and useful red-flag/verification sections, but it is undermined by the missing bundle: every detailed module it points to is absent, and its steps describe commands in prose instead of providing executable code. Conciseness is acceptable but padded with known-concept justifications, duplicated module listings, and conflicting version stamps.

Suggestions

Ship the modules/ directory (component-architecture.md, design-system-tokens.md, accessibility-wcag.md, icon-libraries.md, theming-system.md, web-interface-guidelines.md) or inline the essential detail — as written, the skill's substance is all behind dead references; also correct the paths for examples.md and reference.md to references/.

Add executable commands and code to the Quick Start workflows (e.g. the actual Style Dictionary build command, the shadcn init/add commands, and a sample DTCG token JSON) instead of describing them in prose like 'running the init command'.

Trim the justifications for well-known practices in Best Practices, deduplicate the Module Organization vs Quick Decision Guide listings, and remove the conflicting trailing 'Last Updated / Version' block that contradicts the frontmatter.

DimensionReasoningScore

Conciseness

The body is mostly tight list-form, but includes unnecessary explanation of concepts Claude already knows ("Screen readers cannot interpret visual icons without text alternatives", "Namespace imports bundle entire libraries, defeating tree-shaking optimization"), duplicates the module pointers in both 'Module Organization' and 'Quick Decision Guide', and carries conflicting time-sensitive stamps ("Last Updated: 2026-03-11 ... Version: 3.0.0" vs frontmatter 2026-03-28 / 3.1.0). Too much padding for a 4, but far from the heavily padded anchor-2 example.

3 / 5

Actionability

The workflows give concrete specifics (file names, library names, token formats like 'type color and primary 500 value') but never provide executable code or commands — 'running the build command', 'running the init command', and 'installing the package' name commands without giving them, and no code block appears anywhere in the body. This matches anchor 3 (guidance present but incomplete, effectively verbal pseudocode) rather than anchor 4's executable guidance.

3 / 5

Workflow Clarity

Four multi-step workflows are clearly sequenced and an end-of-file Verification checklist exists ('Color contrast meets WCAG AA (4.5:1 normal text...)'), but the workflows themselves have no per-step validation checkpoints — steps simply end with 'See modules/... for the complete guide'. This sits at anchor 3 (sequence present, checkpoints implicit) rather than anchor 4 (most checkpoints present within the workflow).

3 / 5

Progressive Disclosure

The body is genuinely structured as an overview with a dedicated 'Module Organization' section clearly signaling references, but scored against the actual bundle: all seven referenced 'modules/*.md' files (component-architecture, design-system-tokens, accessibility-wcag, icon-libraries, theming-system, web-interface-guidelines, examples) do not exist in the bundle — only references/examples.md and references/reference.md are present, and the body cites them without the references/ path prefix. The organization intent is anchor-4, but the broken navigation is more than 'minor organization gaps', capping it at anchor 3.

3 / 5

Total

12

/

20

Passed

Description

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

A solid description with an explicit 'Use when' clause and good natural trigger terms. Its main weakness is that the what-clause enumerates coverage areas via a role label ('specialist covering X') rather than concrete actions, and the trigger list covers only part of the claimed scope.

Suggestions

Replace the topic enumeration with concrete actions, e.g. 'Implements WCAG 2.2-compliant components, sets up DTCG design token pipelines, configures light/dark theming, and selects/integrates icon libraries'.

Add missing natural trigger terms to the 'Use when' clause — 'UI', 'UX', 'component library', 'responsive design', and framework names like React, Vue, shadcn/ui, Tailwind — so the when-clause matches the breadth of the what-clause.

DimensionReasoningScore

Specificity

"UI/UX design systems specialist covering accessibility, icons, theming, design tokens, and user experience patterns" enumerates five concrete coverage areas, but uses no action verbs — it describes topics rather than concrete actions like 'extract' or 'build'. It is more informative than the anchor-2 bare-domain case ('Processes PDF files'), but falls short of anchor 4, which requires several specific named actions.

3 / 5

Completeness

Both parts are present: a what ("UI/UX design systems specialist covering accessibility, icons, theming, design tokens, and user experience patterns") and an explicit when ("Use when working on design systems, WCAG compliance, ARIA patterns, or dark mode theming"). Not a 5 because the what is a role/topic list rather than concrete actions, and the when-clause triggers cover only a subset of the five claimed capability areas (e.g., no icon- or user-experience-pattern trigger). Well above anchor 3, where 'when' is missing or only implied.

4 / 5

Trigger Term Quality

The 'Use when' clause provides natural phrases users would say: "design systems, WCAG compliance, ARIA patterns, or dark mode theming", plus "accessibility", "icons", and "design tokens" in the what-clause. Common variations are missing, however — no 'UI', 'UX', 'component library', 'responsive', or framework terms (React/shadcn) that users frequently mention, so it does not reach the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — design systems, WCAG/ARIA compliance, and dark-mode theming are distinctive triggers unlikely to fire for unrelated skills, matching anchor 4's 'mostly distinct'. Not a 5 because 'user experience patterns' and 'design system' are broad phrases with minor overlap risk against general frontend or CSS-skills.

4 / 5

Total

15

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

modu-ai/moai-adk

Path

.moai/archive/skills/v3.0/moai-domain-uiux/SKILL.md

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.