awwwards-ui-skills

Awwwards's UI design system. Use when building interfaces inspired by Awwwards's aesthetic - light mode, Inter font, 4px grid.

Quality

62%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/awwwards/SKILL.md

Quality

Discovery

75%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has a clear 'Use when' clause and is distinctive enough to avoid conflicts with other skills. However, it lacks specific concrete actions (what the skill actually does beyond being a 'design system') and could benefit from more natural trigger terms that users might use when requesting this type of design work.

Suggestions

Add concrete actions the skill performs, e.g., 'Applies Awwwards-inspired styling to UI components, creates layouts on a 4px grid, configures Inter typography scales.'

Include additional natural trigger terms users might say, such as 'modern design', 'award-winning UI', 'clean minimalist interface', or 'Awwwards-style'.

Dimension	Reasoning	Score
Specificity	Names the domain (UI design system) and mentions some specific elements (light mode, Inter font, 4px grid), but doesn't list concrete actions like 'create layouts', 'style components', or 'apply typography rules'.	2 / 3
Completeness	Clearly answers both what ('Awwwards's UI design system') and when ('Use when building interfaces inspired by Awwwards's aesthetic - light mode, Inter font, 4px grid') with an explicit 'Use when' clause and trigger conditions.	3 / 3
Trigger Term Quality	Includes 'Awwwards', 'UI design system', 'light mode', 'Inter font', and '4px grid' which are somewhat relevant, but misses natural user terms like 'modern design', 'award-winning UI', 'clean interface', 'minimalist design', or 'web design'.	2 / 3
Distinctiveness Conflict Risk	The specific reference to 'Awwwards' aesthetic with concrete design tokens (Inter font, 4px grid, light mode) creates a clear niche that is unlikely to conflict with other design system skills.	3 / 3
	Total	10 / 12 Passed

Implementation

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides a comprehensive design system reference with specific values and clear constraint language (MUST/SHOULD/NEVER), which is valuable. However, it reads more like raw design token extraction output than a curated, actionable skill — several values appear to be artifacts (0px input height, inconsistent element widths), there are no code examples showing implementation, and the document could be more concise by separating detailed reference tables from core guidelines.

Suggestions

Add executable code examples showing how to implement the design system (e.g., Tailwind config, CSS custom properties setup, or a sample component)

Review and clean up apparent extraction artifacts: '0px' input height, raw 'Detected Layout Patterns' dimensions, and duplicate 'body-secondary' entries with different values

Split detailed reference tables (full text styles list, all font sizes) into a separate REFERENCE.md and keep SKILL.md as a concise overview with the most important constraints and links

Add a brief workflow section explaining how to apply these constraints when building a new UI component (e.g., start with layout grid, apply typography tokens, then colors)

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with well-structured tables and clear MUST/SHOULD/NEVER constraints, but includes some redundancy (e.g., border-radius scale listed twice, duplicate 'body-secondary' entries, 'Detected Layout Patterns' with raw pixel dimensions that feel like unprocessed data rather than actionable guidance). The '0px height for input fields' is suspicious and likely an extraction artifact rather than intentional design.	2 / 3
Actionability	Provides specific values (hex codes, pixel sizes, font weights) and clear constraint rules (MUST/SHOULD/NEVER), which is good. However, there are no executable code examples showing how to implement these in CSS/Tailwind/any framework, no component code snippets, and some values seem like raw extraction artifacts (e.g., input height '0px', element widths '91px, 58px, 32px') rather than actionable design decisions.	2 / 3
Workflow Clarity	This is primarily a reference/constraint document rather than a multi-step workflow, so explicit sequencing is less critical. However, there's no guidance on the order of applying these constraints when building a UI, no validation steps to check compliance, and no process for resolving conflicts between rules. For a design system skill, a brief 'how to apply' workflow would improve clarity.	2 / 3
Progressive Disclosure	The content is well-organized with clear section headers and tables, making it easy to scan. However, it's a fairly long monolithic document that could benefit from splitting detailed reference tables (all font sizes, all text styles) into separate reference files while keeping the SKILL.md as a concise overview with links.	2 / 3
	Total	8 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ihlamury/design-skills
Commit: 126714e

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