CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

60

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./clawd/skills/frontend-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 compact, well-structured creative-guidance body with a clear think-then-implement workflow and good section organization. Its weaknesses are repetition of the anti-generic message, motivational padding, and the absence of any concrete example (font pairing, palette, or code snippet) that would make the aesthetic guidance directly executable.

Suggestions

Consolidate the repeated 'avoid generic AI aesthetics' warnings (currently stated in the intro, the guidelines, and the closing) into one authoritative list of anti-patterns to save tokens.

Add one concrete executable anchor — e.g., a minimal CSS snippet demonstrating staggered animation-delay reveals or an example display/body font pairing — to lift actionability.

Turn the implementation criteria bullets into an explicit post-build self-review checklist step at the end of the workflow to add a validation checkpoint.

DimensionReasoningScore

Conciseness

The body is mostly efficient directives, but the avoid-generic-aesthetics point is repeated at least three times ("avoid generic 'AI slop' aesthetics", "NEVER use generic AI-generated aesthetics", "NEVER converge on common choices"), and motivational padding like "Remember: Claude is capable of extraordinary creative work. Don't hold back" could be trimmed. Not a 2 because each section still contributes distinct guidance.

3 / 5

Actionability

Some concrete guidance exists (named techniques like "staggered reveals (animation-delay)", "Motion library for React", gradient meshes, grain overlays, a tone list, and named fonts to avoid), but there are no executable artifacts — no example font pairing, sample palette, or CSS snippet — leaving key details open, which fits anchor 3 rather than 4.

3 / 5

Workflow Clarity

A clear two-phase sequence is present ("Before coding, understand the context and commit to a BOLD aesthetic direction" followed by implementation criteria), and the bullets "Production-grade and functional / Visually striking / Cohesive / Meticulously refined" act as an implicit checklist. It sits below anchor 5 only because there is no explicit self-review step against that checklist.

4 / 5

Progressive Disclosure

The body is ~40 well-organized lines with clear sections (Design Thinking, Frontend Aesthetics Guidelines), no bundle files exist, and no external references are needed; per the rubric's simple-skill guidance, a self-contained skill under 50 lines with well-organized sections scores at the top.

5 / 5

Total

15

/

20

Passed

Description

78%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 description in third-person voice with an explicit 'Use this skill when...' clause and concrete trigger phrases. Its main weakness is that the stated actions (create/build/generate) are synonymous abstractions rather than several distinct concrete capabilities, and a few natural trigger synonyms (UI, website, design) are missing.

DimensionReasoningScore

Specificity

The description names the domain ("frontend interfaces") and 1-2 concrete actions ("build web components, pages, or applications"; "Generates creative, polished code"), but create/build/generate are near-synonyms rather than the several distinct concrete actions that anchor 4 requires.

3 / 5

Completeness

Explicitly answers both what ("Create distinctive, production-grade frontend interfaces... Generates creative, polished code that avoids generic AI aesthetics") and when ("Use this skill when the user asks to build web components, pages, or applications") with concrete trigger phrases, matching the anchor 5 pattern rather than anchor 4's 'when could be more explicit'.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ("build web components, pages, or applications", "frontend") with good keyword coverage; a few common terms like "UI", "website", or "design" are missing, placing it just below anchor 5.

4 / 5

Distinctiveness Conflict Risk

The design-quality niche ("avoids generic AI aesthetics") is clearly distinct, but the trigger phrase "build web components, pages, or applications" is broad enough to overlap with general frontend build requests — mostly distinct with minor overlap risk.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

stukennedy/openclaw-starter-kit

Path

clawd/skills/frontend-design/SKILL.md

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.