CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

stitch-design-taste

Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.

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 ./skills/stitch-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 content is highly actionable, packed with exact values, named fonts, and a complete output template, and its nine-step process is clearly sequenced. Its weaknesses are redundancy — bans restated across sections and three closing sections that restate earlier rules — and the absence of a validation/review checkpoint on the generated output. Trimming the repeats and moving the output template to a reference file would tighten it considerably.

Suggestions

Consolidate the repeated bans: state each rule once and let the anti-pattern list reference sections (e.g., 'see Color Mapping') instead of restating the Inter, pure-black, centered-hero, and 3-column bans a second time.

Merge 'Best Practices', 'Tips for Success', and 'Common Pitfalls' into a single short section — they largely restate the numbered rules — or fold their few unique points back into those rules.

Add a final verification step to the workflow, e.g., 'Review the generated DESIGN.md against the anti-pattern list before delivering it', to close the validation gap.

Move the full DESIGN.md output template into a references/ file (e.g., references/template.md) and link to it, shortening SKILL.md and improving progressive disclosure.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive with no over-explanation of concepts Claude already knows, but redundancy is noticeable: the same bans appear twice (e.g., 'Inter is BANNED' in the typography section and again in the anti-pattern list; 'Never use pure black' in color mapping and again as an anti-pattern; the centered-hero and 3-column bans each repeated), and the 'Best Practices', 'Tips for Success', and 'Common Pitfalls' sections largely restate earlier rules. Fits anchor 3 — mostly efficient but could be tightened — rather than 4, where trims would be minor.

3 / 5

Actionability

Fully concrete, executable guidance for an instruction-only skill: exact values ('stiffness: 100, damping: 20', 'max 65 characters per line', '44px tap target', 'min-h-[100dvh]', 'clamp(3rem, 8vw, 6rem)'), named font options, and a complete copy-ready DESIGN.md output template with worked examples like 'Charcoal Ink (#18181B) — Primary text, Zinc-950 depth'. Matches anchor 5: the common cases are fully covered with specific, ready-to-use material.

5 / 5

Workflow Clarity

Steps 1–9 ('Define the Atmosphere' through 'List Anti-Patterns') form a clear, well-sequenced analysis-and-synthesis process culminating in a structured output format. No validation or review checkpoint exists (e.g., verifying the generated DESIGN.md against the anti-pattern list), so it fits anchor 4 (clear sequence, minor validation gaps) rather than 5; the skill is document generation, not a destructive or batch operation, so the workflow cap does not apply.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the single-file body is well-sectioned with clear headers and no nested or buried references. The ~180-line body inlines a full output template and long anti-pattern/typography lists that could live in reference files, which keeps it at anchor 4 (good structure, minor organization gaps) rather than 5.

4 / 5

Total

16

/

20

Passed

Description

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

The description is specific and distinct, clearly stating what the skill produces and the standards it enforces with concrete design vocabulary. Its main weakness is the absence of any 'Use when...' trigger clause, leaving the activation context only implied. Adding an explicit trigger (e.g., 'Use when generating or refining screens in Google Stitch...') would lift completeness.

Suggestions

Append an explicit trigger clause, e.g., 'Use when generating new screens or design systems in Google Stitch, or when a user mentions Stitch, DESIGN.md, or wanting premium/anti-generic UI design.'

Add one or two natural user phrasings as trigger synonyms (e.g., 'design language', 'make my Stitch designs look premium') to broaden trigger term coverage.

State the input context alongside the output (e.g., 'translates a user's vibe description into...') to sharpen what the skill acts on.

DimensionReasoningScore

Specificity

Names the concrete artifact ('Generates agent-friendly DESIGN.md files') and enumerates the specific standards enforced (strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, hardware-accelerated performance). Matches anchor 4 — several specific capabilities with minor gaps — rather than 5, which would require multiple distinct actions beyond a single generative task.

4 / 5

Completeness

The 'what' is clear (generates DESIGN.md files enforcing premium UI standards), but there is no 'Use when...' clause or equivalent explicit trigger guidance; usage context is only weakly implied through 'Google Stitch'. Per the judging guideline, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural keywords a user would say ('Google Stitch', 'design system', 'DESIGN.md', 'UI standards', 'typography', 'color'), but misses common variations such as 'design language', 'UI generation', or 'make screens look premium'. Good coverage with a few natural terms missing fits anchor 4, not the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

'Semantic Design System Skill for Google Stitch' plus DESIGN.md generation carves a fairly distinct niche with specific triggers, though it could minorly overlap with general UI/design-styling skills. Mostly distinct with minor overlap risk fits anchor 4.

4 / 5

Total

15

/

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

Leonxlnx/taste-skill

Path

skills/stitch-skill/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.