design-system

Guide for using Sentry's layout and text primitives. Use when implementing UI components, layouts, or typography. Enforces use of core components over styled components.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/design-system/SKILL.md

Quality

Content

77%Weight 40%Scale 1-3

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 with concrete, copy-paste-ready examples and clear decision/approval workflows. Its weak spots are token-efficiency (repeated inheritance explanations) and the absence of a progressive-disclosure structure that splits the extensive reference material into separate files.

Suggestions

State the Container-prop inheritance once and reference it from Flex/Grid/Stack instead of repeating the 'Plus ALL Container props' block verbatim.

Move the token reference tables and full prop listings into a separate reference file (e.g. references/props-and-tokens.md) and link to it from the overview, reducing the inline length.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining concepts Claude already knows, but the Container-prop inheritance is explained in a blockquote and then repeated verbatim per component ('Plus ALL Container props: position, padding, margin...'), which could be stated once, matching the 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	It provides numerous concrete, copy-paste-ready TSX examples with imports, explicit props, and paired wrong/right patterns for every primitive, matching the 'fully executable code/commands; specific examples; copy-paste ready' anchor.	3 / 3
Workflow Clarity	The 'Creating Thin Abstractions' section is a clear numbered sequence with an explicit approval checkpoint ('Wait for explicit approval before proceeding'), and the 'Quick Reference Checklist' gives a concrete decision workflow, satisfying clear sequencing with explicit checkpoints.	3 / 3
Progressive Disclosure	The file is well-organized into sections and signals external implementation files clearly ('see container.tsx for complete list'), but no bundle reference files exist and large reference material (token tables, full prop listings) is inline in a ~519-line file rather than split out, fitting the 'content that should be separate is inline' anchor.	2 / 3
	Total	10 / 12 Passed

Description

75%Weight 40%Scale 1-3

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 cleanly answers both what the skill does and when to use it, with an explicit 'Use when' trigger and a distinct Sentry-specific niche. Its main weakness is trigger-term breadth and that the named actions are broad categories rather than a sharp list of concrete operations.

Suggestions

Broaden trigger terms to include natural variations users might say, e.g. 'styling', 'flex/grid layout', 'CSS', or 'Emotion'.

Sharpen the capability list into concrete actions (e.g. 'build flex/grid/stack layouts, apply spacing/border/radius tokens, add tooltips') rather than broad categories.

Dimension	Reasoning	Score
Specificity	The description names the domain ('layout and text primitives') and several action areas ('implementing UI components, layouts, or typography', 'use of core components over styled components'), but these are broad categories rather than a list of distinct concrete operations, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It explicitly answers both 'what' ('Guide for using Sentry's layout and text primitives', 'Enforces use of core components over styled components') and 'when' ('Use when implementing UI components, layouts, or typography'), matching the anchor for clearly answering both what and when with explicit triggers.	3 / 3
Trigger Term Quality	It includes relevant natural keywords ('UI components', 'layouts', 'typography', 'styled components') but is missing common variations a user might say such as 'styling', 'flex/grid', 'CSS', or 'Emotion', fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Tying the skill to 'Sentry's layout and text primitives' and enforcing '@sentry/scraps' core components over styled components carves out a clear, codebase-specific niche with distinct triggers unlikely to fire for unrelated UI work.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (523 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: getsentry/sentry
Path: .agents/skills/design-system/SKILL.md
Commit: b4b3565

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