CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ui-design

Use when users need visual direction, interface hierarchy, layout decisions, design specifications, or prototypes before implementing a Web or mini program UI.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./config/.claude/skills/ui-design/SKILL.md

The canonical home for this skill is ui-design in TencentCloudBase/CloudBase-AI-Toolkit

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 delivers exceptionally concrete, executable design guidance with a clear process and self-validation loop, but it is noticeably bloated by duplicated activation sections and prohibitions repeated four times over, and its file structure is monolithic with a broken checklist.md reference. Deduplicating the rules and splitting detailed guidelines into reference files would raise both conciseness and organization.

Suggestions

Merge the "Activation Contract" and "When to use this skill" sections into a single activation block, and state the forbidden colors/fonts/emoji rules once in the Design Specification section with the self-audit referencing them instead of restating them.

Move the detailed Frontend Aesthetics Guidelines (scene judgement table, grid/spacing rules, anti-pattern code examples) into a references/ file such as references/aesthetics.md, keeping SKILL.md as a lean overview with one-level-deep, clearly signaled links.

Ship the referenced checklist.md in the bundle or remove the "Read [UI Design Activation Checklist](checklist.md)" link, since the file is currently missing and the link cannot be followed.

DimensionReasoningScore

Conciseness

The body duplicates its activation guidance in two separate sections ("Activation Contract" and "When to use this skill", each with its own "Do NOT use for" list) and repeats the forbidden color/font/emoji prohibitions roughly four times across the checklist, typography, anti-pattern, and self-audit sections. This is several padded sections of redundant content rather than occasional tightening opportunities, matching anchor 2; it avoids a 1 because it never explains basic concepts Claude already knows.

2 / 5

Actionability

Guidance is fully executable: exact hex ranges for forbidden colors, copy-paste grep audit commands, concrete curl/Invoke-WebRequest download commands, numeric constraints (≥4.5:1 contrast, 65–75ch measure, 4-based spacing scale), a fill-in design specification template, and paired ❌/✅ code examples covering the common cases — matching the anchor-5 example.

5 / 5

Workflow Clarity

The six-step design process is clearly sequenced with a mandatory pre-code specification gate, and the self-audit checklist provides explicit validation commands plus a feedback loop ("If any audit fails → Re-design with correct approach") and a trigger-word detector with a recovery path — satisfying anchor 5's sequence, checkpoints, and error-recovery criteria.

5 / 5

Progressive Disclosure

Section headers give the ~380-line body reasonable structure, but all detail (aesthetics rules, anti-pattern code, audit scripts) is inlined in SKILL.md rather than split into reference files, the only internal reference — "Read [UI Design Activation Checklist](checklist.md)" — points to a file that does not exist in the bundle, and the ../web-development sibling links are explicitly unresolvable in standalone installs. This is unambiguous structure with real reference defects, fitting anchor 3 rather than 4.

3 / 5

Total

15

/

20

Passed

Description

75%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 well-scoped, trigger-first description that clearly identifies the design-phase niche and when to use it. It would score higher by stating the skill's actions in third person (e.g., "Produces design specifications, aesthetic directions, and high-fidelity prototypes") and adding common synonyms such as "look and feel" or "style".

DimensionReasoningScore

Specificity

The description names five concrete deliverables — "visual direction, interface hierarchy, layout decisions, design specifications, or prototypes" — giving specific scope, but they are stated as objects the user needs rather than actions the skill performs, so it falls short of the comprehensive action-verb coverage of a 5.

4 / 5

Completeness

The "when" is explicit and concrete ("Use when users need … before implementing a Web or mini program UI"), and the deliverable list implies the "what", but the skill's actions are never stated directly — the "what" could be more explicit, matching anchor 4 rather than 5.

4 / 5

Trigger Term Quality

Includes natural phrases users would say such as "visual direction", "layout decisions", "design specifications", "prototypes", and "Web or mini program UI". Common synonyms like "look and feel", "style", "wireframe", or "UI design" are missing, keeping it below a 5.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — pre-implementation design decisions for Web and mini-program UIs — with distinct triggers, though it has minor overlap risk with general frontend/web-development skills, which the body itself acknowledges as sibling skills.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 possibly missing (checklist.md)

Warning

referenced_paths_exist

Referenced path issues: 1 possibly missing (assets/images/logo.png), 1 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

TencentCloudBase/CloudBase-AI-Toolkit

Path

config/.claude/skills/ui-design/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.