CtrlK
BlogDocsLog inGet started
Tessl Logo

laws-of-ux

Review and guide UI implementations using the 21 Laws of UX. Identifies usability issues in HTML, CSS, and JavaScript by applying established cognitive, visual, and behavioral principles. Use when reviewing UI code, building new interfaces, or auditing user experience.

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with concrete code examples and specific review thresholds, but it is long and monolithic — restating concepts Claude already knows and keeping all 21 laws inline rather than splitting them into one-level-deep reference files. A leaner overview pointing to category reference files, plus a verify-findings checkpoint, would lift conciseness, workflow clarity, and progressive disclosure.

Suggestions

Move the per-law definitions and example pairs into one-level-deep reference files (e.g., references/cognitive-laws.md, references/visual-laws.md, references/behavioral-laws.md) and keep SKILL.md as a concise overview + checklist with clearly signaled links, improving both conciseness and progressive disclosure.

Trim the well-known law definitions (Miller's 7±2, Fitts's distance/size, Jakob's "users spend most time on other sites") to a phrase or omit them, since Claude already knows these; retain only the code-oriented 'What to look for' and 'Review flags' to earn conciseness at the 3 anchor.

Add an explicit review workflow with a validation checkpoint — e.g., '1. Scan the Review Checklist, 2. Cite the most relevant law per issue, 3. Verify the finding against the code before reporting' — and note the Cross-Cutting Concerns dedup step as a required final pass to push workflow clarity toward 3.

DimensionReasoningScore

Conciseness

The body is mostly efficient with short one-line definitions and concrete examples, but it re-states well-known UX law definitions Claude already knows (e.g., Miller's 7±2, Fitts's distance/size) and runs ~970 lines that could be tightened; it sits above the verbose score-1 anchor but below the lean score-3 anchor.

2 / 3

Actionability

Provides copy-paste-ready GOOD/BAD HTML and CSS code examples and concrete review-flag thresholds (">7 top-level items", "min-height: 44px", ">10 ungrouped options"), matching the fully-executable score-3 anchor.

3 / 3

Workflow Clarity

A usable sequence exists — "check the Review Checklist first, then refer to the detailed sections" plus Cross-Cutting Concerns grouping — but there are no explicit validation checkpoints or feedback loops (e.g., verify findings before reporting), so it lands at the steps-present-but-checkpoints-implicit score-2 anchor.

2 / 3

Progressive Disclosure

The body is well-sectioned (checklist, three law categories, cross-cutting concerns) but is a single ~970-line monolithic file with no bundle references (references/, scripts/, assets/ are absent); content that could be split into per-category reference files is inlined, matching the score-2 anchor.

2 / 3

Total

9

/

12

Passed

Description

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.

The description is strong: it names concrete actions, provides explicit "Use when..." trigger guidance with natural keyword variations, and occupies a clear niche unlikely to conflict with other skills. No first/second-person voice issues are present (third person is used throughout).

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Review and guide UI implementations", "Identifies usability issues in HTML, CSS, and JavaScript", and "auditing user experience" — matching the score-3 anchor of multiple specific concrete actions.

3 / 3

Completeness

Clearly answers both what it does (review/guide UI, identify usability issues) and when to use it via an explicit "Use when..." clause, matching the score-3 anchor.

3 / 3

Trigger Term Quality

Includes natural terms users would say — "reviewing UI code", "building new interfaces", "auditing user experience" — plus a rich metadata trigger set (ux review, ui review, usability, ux audit), giving good coverage of natural phrasings.

3 / 3

Distinctiveness Conflict Risk

A clear niche — the 21 Laws of UX applied to HTML/CSS/JS UI implementations — with distinct triggers that are unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (980 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository
RoleModel/rolemodel-skills
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.