design-check

Audit UI code against the Mediatheca design system. Checks F# (Fable/Feliz) view files and CSS for violations of glassmorphism rules, typography hierarchy, theme tokens, DesignSystem.fs usage, backdrop-filter nesting, spacing/layout conventions, animation standards, and DaisyUI 5 patterns. Use when the user asks to "design check", "check design", "audit styles", "review UI code", "check glassmorphism", or any request to verify UI code follows the design system.

2.82x

Quality

89%

Does it follow best practices?

Impact

99%

2.82x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

79%

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, concise skill that provides clear actionable guidance for auditing UI code against a design system. Its main strengths are token efficiency and a concrete output format with severity classification. The primary weakness is the lack of a re-validation step after auto-fixing violations, and the referenced design-rules.md file is not available in the bundle to verify.

Suggestions

Add a re-validation step after auto-fixing: re-run the audit on fixed files to confirm violations are resolved before reporting completion.

Include the `references/design-rules.md` file in the bundle, or note what to do if it's missing.

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient. It doesn't explain what glassmorphism is, what DaisyUI is, or how F#/Fable works—it assumes Claude knows all of this. Every section serves a clear purpose with no padding.	3 / 3
Actionability	Provides a concrete git command for file discovery, specifies exact file paths to read (DesignSystem.fs, design-rules.md), lists all 9 rule categories explicitly, and gives a complete report template with table format and severity classification. The example violation row is copy-paste ready.	3 / 3
Workflow Clarity	The 6-step workflow is clearly sequenced and logical. However, there are no validation checkpoints or feedback loops—for instance, after auto-fixing violations there's no step to re-run the audit to verify fixes were correct. For an audit workflow that offers to auto-fix code, a re-validation step is important.	2 / 3
Progressive Disclosure	The skill references `references/design-rules.md` for the full rule set, which is good progressive disclosure. However, no bundle files are provided, so we can't verify this reference exists. The 9 rule categories are listed inline as a summary which is appropriate, but the skill could benefit from clearer signaling of what's in the referenced file versus what's here.	2 / 3
	Total	10 / 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.

This is an excellent skill description that clearly defines its purpose, lists comprehensive specific capabilities, and provides explicit trigger terms. It uses proper third-person voice throughout and covers a highly specific niche (Mediatheca design system with F#/Fable/Feliz) that minimizes conflict risk with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: checks F# (Fable/Feliz) view files and CSS for violations of glassmorphism rules, typography hierarchy, theme tokens, DesignSystem.fs usage, backdrop-filter nesting, spacing/layout conventions, animation standards, and DaisyUI 5 patterns.	3 / 3
Completeness	Clearly answers both 'what' (audits UI code against the Mediatheca design system, checking specific rules) and 'when' (explicit 'Use when...' clause with multiple trigger phrases and a general catch-all for verifying UI code follows the design system).	3 / 3
Trigger Term Quality	Includes natural trigger phrases users would say: 'design check', 'check design', 'audit styles', 'review UI code', 'check glassmorphism', plus domain-specific terms like 'glassmorphism', 'DaisyUI 5', 'Fable/Feliz', and 'design system' that help with precise matching.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: specific to the Mediatheca design system, F#/Fable/Feliz stack, glassmorphism rules, and DaisyUI 5 patterns. Very unlikely to conflict with other skills due to the unique technology stack and domain specificity.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: heimeshoff/Mediatheca
Commit: 1b0eba4

Reviewed: 27 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.