CtrlK
BlogDocsLog inGet started
Tessl Logo

stave-design-system

Apply Stave's desktop-first design system when a task changes UI, layout, theme, dialogs, sidebars, empty states, settings, prompt input, or other visual UX in this repo. Use for prompts like "디자인", "UI", "redesign", "polish", "sidebar", "dialog", "settings", or whenever a new interface pattern is introduced. Always use existing shadcn components and the radix-vega preset first — never hand-roll a control that shadcn already provides.

72

Quality

88%

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

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.

A well-structured, highly actionable design skill body that gives concrete commands, paths, and decision rules without over-explaining. Workflow and disclosure are strong with only minor tightening opportunities.

Suggestions

Add an explicit validate→fix→retry loop to the Implementation Workflow (e.g., 'if light/dark or split-panel check fails, fix and re-check before moving on') to push workflow_clarity toward 5.

Trim prose in 'Glass and Depth' and 'Stave-Specific Product Guidance' into tighter bullets to improve conciseness.

Consider moving the full shadcn component inventory table into a reference file (e.g. references/component-inventory.md) referenced from the body, to reduce inline weight and improve progressive_disclosure.

DimensionReasoningScore

Conciseness

Mostly lean, actionable rules and inventories with no padding about concepts Claude already knows; a few prose sections ('Glass and Depth', 'Stave-Specific Product Guidance') could be tightened without losing meaning.

4 / 5

Actionability

Provides an executable command ('bunx --bun shadcn@latest add <component> --yes'), exact file paths, a concrete component inventory table, and copy-ready decision rules ('Need a boolean toggle? → Use Switch') that cover the common cases.

5 / 5

Workflow Clarity

The 'Implementation Workflow' is a clear 8-step sequence with verification checkpoints (light/dark, split-panel widths) and a QA checklist; it lacks an explicit validate→fix→retry feedback loop, but the work is not destructive or batch so no cap applies.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and a 'Read First' list of one-level-deep, clearly signaled repo file references; no nested references. It inlines the full inventory and Do/Don't lists that are appropriately placed, with only minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

95%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, well-scoped description that clearly states both the capability and the natural trigger conditions in two languages. It is concrete and distinct rather than generic.

DimensionReasoningScore

Specificity

Names the domain ('Apply Stave's desktop-first design system') plus concrete surfaces (dialogs, sidebars, empty states, settings, prompt input) and a hard rule ('use existing shadcn components and the radix-vega preset first — never hand-roll'), but enumerates surfaces/triggers rather than a comprehensive list of discrete actions, leaving minor gaps.

4 / 5

Completeness

Explicitly answers what ('Apply Stave's desktop-first design system... use existing shadcn components and the radix-vega preset first') and when ('Use for prompts like... or whenever a new interface pattern is introduced') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including bilingual terms ('디자인'), synonyms ('UI', 'redesign', 'polish'), and concrete surface names ('sidebar', 'dialog', 'settings') a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Tightly scoped to this repo's design system with a named preset (radix-vega) and surface-specific triggers, giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

19

/

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
sendbird/stave
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.