CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

62

Quality

74%

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

82%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 with precise, executable values and a clear nine-step workflow supported by a complete output template. Its only weaknesses are minor conciseness trimming opportunities and a few implicit rather than explicit verification checkpoints.

Suggestions

Add an explicit validation/review checkpoint before finalizing the DESIGN.md (e.g., a 'Verify against the anti-pattern list' step) to close the workflow-clarity gap.

Consider extracting the full DESIGN.md output template and the exhaustive anti-pattern list into a references file to tighten the main body.

Trim the 'Best Practices' and 'Tips for Success' sections, which partly restate rules already covered above.

DimensionReasoningScore

Conciseness

The body is dense and opinionated with no padding of concepts Claude already knows (e.g., it states exact hex codes, font bans, and spring values rather than explaining them), with only minor sections that could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance: precise hex codes, named fonts, spring physics values ("stiffness: 100, damping: 20"), clamp() expressions, breakpoint pixel values, and a complete DESIGN.md output template covering common cases.

5 / 5

Workflow Clarity

A clearly sequenced nine-step analysis process (Atmosphere → Color → Typography → Hero → Components → Layout → Responsive → Motion → Anti-patterns) with constraint-style checkpoints; this is a generation task so the destructive/batch validation cap does not apply, but explicit verification steps are still minor gaps.

4 / 5

Progressive Disclosure

No bundle files exist (references/scripts/assets absent) and the skill is well-organized into clearly headed sections; some inlined material (the full output template, exhaustive ban lists) could be split out, but structure and navigation are good.

4 / 5

Total

17

/

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 well-targeted to a distinct niche, with good trigger-term coverage. Its main weakness is the absence of an explicit "Use when..." clause in the description itself, leaving the "when" only weakly implied.

Suggestions

Add an explicit 'Use when...' clause to the description, e.g. 'Use when generating or refining a Stitch DESIGN.md for premium, non-generic UI.'

Include common natural synonyms in the description (e.g. 'design system', 'UI design language') alongside the existing triggers.

Lead with the single highest-value concrete action before enumerating the enforced standards to sharpen the 'what'.

DimensionReasoningScore

Specificity

Lists several concrete actions/aspects — "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" — covering typography, color, layout, motion, and performance with minor gaps.

4 / 5

Completeness

The description clearly states what the skill does but lacks an explicit "Use when..." clause; the "when" is only weakly implied via the separate triggers field, so per the rubric this caps completeness at 3.

3 / 5

Trigger Term Quality

Triggers include natural phrases users would say ("stitch design taste", "generate DESIGN.md", "semantic design system", "premium design system") giving good keyword coverage, though a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

It targets a clear niche (Stitch DESIGN.md generation with a curated premium aesthetic) that is mostly distinct from other design skills, with only minor overlap risk.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.