claymorphism

Claymorphism design system skill. Use when building soft, puffy, clay-like UI components with large radii, dual inner shadows, and offset outer shadows.

Quality

86%

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

86%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 tight, executable claymorphism spec with copy-paste component examples, accessibility and dark-mode notes, and a single well-placed token reference. Minor duplication of the card example and slight underspecification of shadow-variant selection keep it just short of perfect.

Suggestions

Remove the near-duplicate .clay-card block: keep it in one section and reference it from the other to avoid redundancy.

Add a brief note on when to use --clay-shadow vs --clay-shadow-elevated vs --clay-shadow-pressed so component choice is unambiguous.

Consider a one-line 'How to apply' summary linking the core elements to the token names for faster lookup.

Dimension	Reasoning	Score
Conciseness	Lean, code-forward spec that assumes Claude's competence and avoids explaining basic CSS, but the `.clay-card` block is near-duplicated across the 'CSS Tokens' and 'Card' sections, a minor redundancy that could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready CSS for the common cases (card, button, input, toggle) using concrete design tokens, with hover/active/focus states covered.	5 / 5
Workflow Clarity	The single-purpose task (apply clay tokens/patterns to components) is unambiguous and well-organized, but there is minor implicit guidance on when to choose shadow variants (e.g. pressed vs elevated) per component context.	4 / 5
Progressive Disclosure	Clear overview with a well-signaled, one-level-deep reference to the real file references/tokens.css; token bulk is split out while examples stay inline, making navigation easy.	5 / 5
	Total	18 / 20 Passed

Description

87%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-crafted description that clearly states the design niche, gives concrete visual attributes, and provides an explicit 'Use when' trigger. It is distinct from other UI/design skills and uses appropriate third-person trigger phrasing.

Dimension	Reasoning	Score
Specificity	Names the domain ('claymorphism design system', 'building soft, puffy, clay-like UI components') and lists several concrete defining attributes ('large radii, dual inner shadows, and offset outer shadows'), with only minor coverage gaps versus a fully comprehensive action list.	4 / 5
Completeness	Explicitly answers both 'what' (claymorphism design system for building clay-like UI components) and 'when' via a concrete 'Use when building soft, puffy, clay-like UI components...' trigger clause.	5 / 5
Trigger Term Quality	Includes natural terms a user would say ('soft, puffy, clay-like UI components') alongside the technical 'Claymorphism', giving good keyword coverage, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	'Claymorphism' is a highly specific design niche with distinct triggers (clay-like, puffy, dual inner shadows), giving minimal conflict risk with other skills.	5 / 5
	Total	18 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: fengshao1227/ccg-workflow
Path: templates/skills/domains/frontend-design/claymorphism/SKILL.md
Commit: f349e3d

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