typeui-fundamentals

Universal UI/UX design principles covering visual hierarchy, interaction laws, typography foundations, and WCAG accessibility requirements. Use when making design decisions not covered by a specific design system, validating principle compliance, or resolving conflicts between aesthetics and accessibility. Design-system-agnostic and applies to every surface.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%Weight 40%Scale 1-3

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

A clean, well-organized overview with clear load order and conflict precedence, but its value depends on five referenced module files that are missing from the bundle, leaving the actual instruction content and progressive disclosure unrealized.

Suggestions

Bundle the five referenced module files (ui-principles.md, spacing-principles.md, ux-principles.md, typography-principles.md, accessibility.md) or remove the links so progressive disclosure resolves to real content.

Add a brief inline fallback rule or one concrete example so the SKILL.md body remains actionable even before the module files are loaded.

Collapse the "Conflict resolution" and "When the design system is silent" sections, which restate the same design-system-wins rule, to remove the minor redundancy.

Dimension	Reasoning	Score
Conciseness	The body is lean (~40 lines), assumes Claude's competence, and avoids explaining basic concepts; the only minor redundancy is the overlap between the "Conflict resolution" and "When the design system is silent" sections.	3 / 3
Actionability	It gives concrete structural guidance (numbered conflict-resolution precedence, load order) but the core actionable design instructions are deferred to the five referenced module files, which are not present in the bundle, leaving the actionable detail incomplete here.	2 / 3
Workflow Clarity	The load order is an explicit, clear sequence (design system first, then these files) and conflict resolution is a numbered priority list; as a well-organized overview it meets the simple-skill bar for workflow clarity.	3 / 3
Progressive Disclosure	The body has a well-signaled, one-level-deep module index table, but the five referenced files (ui-principles.md, spacing-principles.md, ux-principles.md, typography-principles.md, accessibility.md) are absent from the bundle, so the disclosure structure is not actually realized.	2 / 3
	Total	10 / 12 Passed

Description

92%Weight 40%Scale 1-3

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 strong description with an explicit Use-when trigger and specific capability areas; its only weakness is breadth that risks overlap with the related design-system skill.

Suggestions

Sharpen distinctiveness by foregrounding the fallback condition, e.g. "Use ONLY when no design system applies" to reduce overlap with the design-system skill.

Lead with a concrete action verb (e.g. "Apply universal UI/UX principles to...") so the opening reads as a capability rather than a topic that is "covered".

Dimension	Reasoning	Score
Specificity	"covering visual hierarchy, interaction laws, typography foundations, and WCAG accessibility requirements" lists multiple specific concrete capability areas rather than vague language, matching the anchor for listing several specific concrete items.	3 / 3
Completeness	It explicitly states what it covers (UI/UX design principles across four areas) and includes an explicit "Use when..." trigger clause answering when to apply it, satisfying both what and when.	3 / 3
Trigger Term Quality	"Use when making design decisions... validating principle compliance, or resolving conflicts between aesthetics and accessibility" plus "design system", "WCAG", "typography" gives good coverage of natural terms the target audience would say.	3 / 3
Distinctiveness Conflict Risk	The "not covered by a specific design system" trigger carves a niche, but "applies to every surface" and "design decisions" are broad enough to overlap with the companion design-system skill, so it is not yet a crisp, conflict-free niche.	2 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 5 missing	Warning

	Total	14 / 16 Passed

Repository: bergside/typeui
Path: skills/fundamentals/SKILL.md
Commit: 2a977f1

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

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.