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.

58

Quality

66%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/stitch-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The body is highly actionable, packed with precise values and a copy-paste-ready DESIGN.md template, and assumes Claude's competence without padding. Its weaknesses are mild redundancy in the repeated banned-patterns lists, no validation checkpoint in the workflow, and a monolithic structure that could offload reference material to bundle files.

Suggestions

Add a final verification checkpoint, e.g. "Before finishing, confirm the DESIGN.md covers all seven sections and that every banned pattern is explicitly listed in §7."

De-duplicate the banned-patterns list — keep it once (Section 9) and have the Output Format reference it rather than restating it.

Move the full DESIGN.md output template and the color/typography reference tables into separate reference files (e.g. references/design-template.md) and link to them, so SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

The ~180-line body avoids explaining concepts Claude already knows (no padding about what fonts or grids are) and is dense with specific values, but the banned-patterns list is repeated three times (Section 9, the Output Format §7, and "Common Pitfalls"), so it could be tightened. It is mostly efficient with mild redundancy, matching score 2 rather than the lean score 3.

2 / 3

Actionability

Guidance is fully concrete and copy-paste ready: exact hex codes (e.g. #18181B, #F9FAFB), precise values (stiffness: 100, damping: 20; min-h-[100dvh]; clamp(3rem, 8vw, 6rem); 44px tap targets; 65ch max-width), and a complete DESIGN.md output template. This matches the score-3 anchor of fully executable, specific examples.

3 / 3

Workflow Clarity

The numbered "Analysis & Synthesis Instructions" (sections 1–9) followed by the Output Format give a clear sequence, but there are no validation or verification checkpoints (e.g., a step confirming the DESIGN.md covers all seven required areas before finishing). Sequence is present but checkpoints are missing, so it is score 2 rather than the checkpointed score 3.

2 / 3

Progressive Disclosure

No bundle files (references/scripts/assets) exist, and the skill is a single ~180-line file with everything inline — the full output template, color/typography reference tables, and anti-pattern lists could be split into separate reference files. Sectioning is clear (well-organized headers), which prevents a 1, but it is monolithic with content that should be separate kept inline, matching score 2.

2 / 3

Total

9

/

12

Passed

Description

67%

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 distinctively scoped to Google Stitch DESIGN.md generation, but it omits any explicit "Use when..." trigger guidance and leans on technical jargon over natural user phrasing. Its main weakness is the missing when-to-use clause, which caps completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when generating design systems or DESIGN.md files for Google Stitch, or when the user wants premium, non-generic UI styling for Stitch screen generation."

Include more natural user-facing terms ("style guide", "brand design", "UI look-and-feel") alongside the technical vocabulary to improve trigger-term coverage.

Trim marketing-flavored adjectives like "premium, anti-generic" in favor of a concrete capability phrase to reduce buzzword density.

DimensionReasoningScore

Specificity

Quotes concrete actions and multiple specific domains: "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." This lists several specific concrete actions, matching the score-3 anchor rather than the partial-coverage score-2 anchor.

3 / 3

Completeness

It clearly answers "what" (generates DESIGN.md enforcing premium UI standards) but provides no "when" guidance — there is no "Use when..." clause or equivalent explicit trigger. Per the judging guidelines, a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

It includes some natural terms a user would say ("Google Stitch", "design system", "DESIGN.md"), but leans technical ("agent-friendly", "anti-generic UI standards", "perpetual micro-motion", "hardware-accelerated") and omits common variations like "style guide", "brand design", or "UI styling". Coverage is partial, so it is score 2, not the comprehensive score 3.

2 / 3

Distinctiveness Conflict Risk

"Semantic Design System Skill for Google Stitch" with a tightly scoped output (DESIGN.md for Stitch screen generation, banned fonts/colors) occupies a clear niche with distinct triggers unlikely to conflict with general design skills, matching the score-3 anchor.

3 / 3

Total

10

/

12

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
Leonxlnx/taste-skill
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.