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.

88

1.35x
Quality

78%

Does it follow best practices?

Impact

96%

1.35x

Average score across 5 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

71%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-structured, opinionated design skill that gives genuinely specific guidance (named fonts to avoid, a named React animation library, concrete techniques like gradient meshes and animation-delay) in a clear think-then-implement sequence. Its main costs are motivational filler and a repeated intentionality point, plus the absence of any starter example to make the guidance immediately executable.

Suggestions

Trim filler to tighten conciseness: remove 'There are so many flavors to choose from' and the 'Remember: Claude is capable of extraordinary creative work' closer, and merge the CRITICAL intentionality note with the IMPORTANT complexity-matching note since they make the same point.

Add one small executable anchor for actionability, e.g. a minimal CSS snippet showing a distinctive font pairing (display + body via @import or font-family stack) and a CSS-variable color scaffold, so the typography and color guidance has a concrete starting point.

Close the workflow loop by adding a brief final self-check step, e.g. 'Before finishing, re-read the output against the chosen tone: does every font, color, and animation serve that direction? Remove anything that does not.'

DimensionReasoningScore

Conciseness

The guidance is mostly dense and useful, but contains padding: 'There are so many flavors to choose from', the motivational closer 'Remember: Claude is capable of extraordinary creative work. Don't hold back...', and the intentionality point stated twice (the CRITICAL note and the IMPORTANT complexity-matching note).

3 / 5

Actionability

Concrete, specific directives throughout — 'Avoid generic fonts like Arial and Inter', 'Pair a distinctive display font with a refined body font', 'Use CSS variables for consistency', 'Prioritize CSS-only solutions', 'Use Motion library for React' — though there are no copy-paste examples such as a starter CSS snippet or font-pairing example to anchor the guidance.

4 / 5

Workflow Clarity

A clear two-phase sequence is present (Design Thinking: Purpose/Tone/Constraints/Differentiation, then commit to a direction, then 'implement working code'), with the tone list acting as a decision point. Minor gap: no review step to check the output against the chosen aesthetic before finishing.

4 / 5

Progressive Disclosure

The skill has no bundle files and the body is under 50 lines with well-organized sections ('Design Thinking', 'Frontend Aesthetics Guidelines') and nothing inlined that belongs in a separate file, matching the simple-skill exception.

5 / 5

Total

16

/

20

Passed

Description

86%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: it explicitly states both what the skill does and when to use it, with an unusually rich set of natural trigger terms for the frontend domain. The only weaknesses are synonymous rather than distinct action verbs and a slightly broad 'any web UI' trigger that could overlap with adjacent styling skills.

DimensionReasoningScore

Specificity

The domain is well-named with a broad inventory of artifact types ('web components, pages, artifacts, posters, or applications'), but the verbs are synonymous variants of a single action (create/build/generate interfaces) rather than multiple distinct concrete operations, so coverage is not comprehensive.

3 / 5

Completeness

It explicitly answers '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 web components, pages, artifacts, posters, or applications') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Phrases like 'websites, landing pages, dashboards, React components, HTML/CSS layouts, styling/beautifying any web UI' comprehensively cover the natural terms users would say when they need this skill, including synonyms.

5 / 5

Distinctiveness Conflict Risk

'avoids generic AI aesthetics' carves out a clear design-quality niche, but the broad trigger 'styling/beautifying any web UI' creates minor overlap risk with closely related styling and design skills.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
microsoft/agent-academy
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.