CtrlK
BlogDocsLog inGet started
Tessl Logo

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

61

Quality

72%

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 ./skills/public/frontend-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body delivers concrete, specific design guidance and executable branding examples within a clear section structure. Its main weaknesses are verbosity in the branding section and a workflow that lacks explicit validation checkpoints.

Suggestions

Trim the eight branding 'Creative Implementation Ideas' to two or three representative patterns and move the rest to a reference file to reduce token overhead in conciseness.

Remove filler and motivational lines (e.g. 'There are so many flavors to choose from' and the closing 'Claude is capable of extraordinary creative work...') that add tokens without actionable value.

Add one or two explicit validation/checkpoint steps to the workflow, such as verifying the branding is subtle and non-distracting and confirming the chosen aesthetic is consistently applied, to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

Mostly on-topic design guidance, but padded with eight branding-implementation variants, filler ('There are so many flavors to choose from'), and a motivational closing ('Claude is capable of extraordinary creative work. Don't hold back ...') that could be trimmed without losing clarity.

3 / 5

Actionability

Names concrete, usable techniques (CSS variables, animation-delay, Motion library for React, gradient meshes, noise textures) and provides copy-paste HTML branding examples; gaps are minor (no complete page/component example), and the instructional design guidance is specific rather than abstract.

4 / 5

Workflow Clarity

A loose sequence exists (Design Thinking considerations -> implement working code -> apply aesthetics -> add branding), but there are no validation checkpoints or feedback loops, and the steps are conceptual rather than strictly sequenced.

3 / 5

Progressive Disclosure

Self-contained with no bundle files and clearly sectioned headers (Design Thinking, Frontend Aesthetics Guidelines, Branding Requirement); at ~86 lines it exceeds the under-50-line simple-skill exception, and the eight-item branding block is somewhat monolithic, so it falls just short of a clean 5.

4 / 5

Total

14

/

20

Passed

Description

83%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-constructed description that clearly answers both what the skill does and when to use it, with concrete and natural trigger terms. It is held back only slightly by repetitive action verbs and some mild fluff in the capability phrasing.

DimensionReasoningScore

Specificity

Lists several concrete actions and many concrete object types ('web components, pages, artifacts, posters, or applications ... websites, landing pages, dashboards, React components, HTML/CSS layouts'), but verbs overlap (create/build/generate) and phrases like 'high design quality' and 'creative, polished' are mildly fluffy, keeping it just below comprehensive.

4 / 5

Completeness

Explicitly states both what ('Create distinctive, production-grade frontend interfaces', 'Generates creative, polished code and UI design') and when ('Use this skill when the user asks to build ... or when styling/beautifying any web UI') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural trigger terms users would actually say ('website', 'landing page', 'dashboard', 'React component', 'poster', 'styling/beautifying any web UI'), but a few common synonyms are missing (e.g. 'mockup', 'prototype', 'web app', 'redesign').

4 / 5

Distinctiveness Conflict Risk

The anti-generic-AI-aesthetic design framing gives a clear niche, but the broad 'build web components, pages ... applications' triggers overlap with general web-development skills, leaving minor conflict risk.

4 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
bytedance/deer-flow
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.