CtrlK
BlogDocsLog inGet started
Tessl Logo

design-standards

Apply production-grade design standards when building or reviewing pages, components, or UI. Use this skill whenever the user asks to build a page, design a component, lay out a section, review the UI, fix the layout, or check design quality. Triggers on build a page, create a component, design a section, hero, card, CTA, layout, review the UI, fix the design, design system, design tokens, spacing, typography scale, button standards, mobile design. Also triggers for any production design decision where contrast, accessibility, spacing, or visual hierarchy matters.

71

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-organized, actionable design-standards skill that uses concrete numbers throughout and cleanly separates overview from one-level-deep references. It could tighten a few basic-principle explanations and add explicit retry loops to its validation steps.

Suggestions

Trim the visual-hierarchy primer ('Size. The largest element gets noticed first', 'Bold beats regular at the same size') — Claude knows these; keep only the design-specific 'Common failures' that add value.

Add an explicit feedback loop to the Workflow validation steps, e.g. after 'Run contrast checks': 'If any combination fails AA, adjust the token and re-check before proceeding.'

Collapse redundant 'Common failures' bullets that merely restate the preceding rule (e.g., touch-target and spacing failure bullets duplicate their standards).

DimensionReasoningScore

Conciseness

Mostly efficient with concrete tables and bullet rules, but a few spots over-explain basics Claude already knows (e.g., 'Size. The largest element gets noticed first. Weight. Bold beats regular at the same size.') and some 'Common failures' items restate the preceding rule.

4 / 5

Actionability

Highly concrete numerical guidance (4.5:1 contrast, 44x44 touch targets, 64px/48px section padding, 375-390px viewport, 16px input text), but it is intentionally stack-agnostic with code deferred to references, leaving a few statements principle-level ('Apply hierarchy intentionally').

4 / 5

Workflow Clarity

The 7-step Workflow is clearly sequenced with validation checkpoints (run contrast checks, test viewport breakpoints, run the pre-ship checklist), but lacks explicit failure feedback loops ('if it fails, fix and re-check'); not a destructive/batch skill so no cap applies.

4 / 5

Progressive Disclosure

SKILL.md is a well-structured overview that points to three real one-level-deep reference files (design-tokens-template.md, preship-checklist.md, tailwind-patterns.md), each clearly signaled via markdown links and a dedicated 'Reference files' section, with content appropriately split.

5 / 5

Total

17

/

20

Passed

Description

96%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 strong, explicit description that clearly states both capabilities and trigger conditions with rich natural keywords. Its only weakness is modest overlap risk with sibling design skills, which the body (not the description) resolves via a 'When NOT to use' section.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'build a page, design a component, lay out a section, review the UI, fix the layout, or check design quality' — giving comprehensive coverage of the skill's capabilities rather than vague abstraction.

5 / 5

Completeness

Explicitly answers both 'what' ('Apply production-grade design standards when building or reviewing pages, components, or UI') and 'when' ('Use this skill whenever the user asks...', 'Triggers on...', 'Also triggers for...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and specifics — 'hero, card, CTA, layout, design system, design tokens, spacing, typography scale, button standards, mobile design, contrast, accessibility' — phrases users would actually say.

5 / 5

Distinctiveness Conflict Risk

Has a clear niche (production design standards for pages/components) but trigger terms like 'design system, design tokens, contrast, accessibility' create minor overlap risk with related brand-identity, design-system, and accessibility-audit skills; the frontmatter does not disambiguate.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
rampstackco/claude-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.