CtrlK
BlogDocsLog inGet started
Tessl Logo

tamagui-best-practices

Provides Tamagui patterns for config v4, compiler optimization, styled context, and cross-platform styling. Must use when working with Tamagui projects (tamagui.config.ts, @tamagui imports).

79

1.77x
Quality

Does it follow best practices?

Impact

94%

1.77x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

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 and code-forward, assuming Claude's competence and avoiding basic-concept filler. Its weaknesses are minor internal redundancy, the absence of validation checkpoints, and reliance on referenced pattern files that are not present in the bundle.

Suggestions

Provide the six referenced pattern files (@DIALOG_PATTERNS.md, @FORM_PATTERNS.md, @ANIMATION_PATTERNS.md, @OVERLAY_PATTERNS.md, @COMPILER_PATTERNS.md, @DESIGN_SYSTEM.md) in a bundle directory, or remove the 'Mandatory Context Loading' pre-read directive and inline the essential guidance.

De-duplicate the '...size' variant-spread example, which appears in both 'Variant Spread Operators' and 'Compound Components with createStyledContext', and remove the trailing 'Additional Pattern Files' list that repeats the context-loading table.

Add a brief validation/checkpoint step where the skill instructs risky operations (e.g., after applying compiler-optimization changes, verify the build still flattens as expected) so the workflow dimension reaches a higher anchor.

DimensionReasoningScore

Conciseness

The body is code-dense and assumes React/TS competence, but the '...size' variant-spread example is repeated across two sections and the trailing 'Additional Pattern Files' list duplicates the 'Mandatory Context Loading' table, so it could be tightened.

2 / 3

Actionability

Provides fully executable TSX throughout — config setup, createThemes, styled variants, a numbered createStyledContext procedure, styleable, the accept prop, and BAD/GOOD anti-patterns — that is copy-paste ready.

3 / 3

Workflow Clarity

One procedure is clearly sequenced (createStyledContext steps 1–4) and a 'read pattern file BEFORE writing code' directive exists, but there are no validation checkpoints or feedback loops and the skill is mostly reference patterns rather than an end-to-end workflow.

2 / 3

Progressive Disclosure

Sections and one-level references are clearly signaled, but the six referenced pattern files (@DIALOG_PATTERNS.md, @FORM_PATTERNS.md, etc.) do not exist in any bundle, so the mandated pre-read cannot actually be performed.

2 / 3

Total

9

/

12

Passed

Description

75%

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 a strong, specific trigger for a well-defined niche, explicitly covering both what the skill does and when to use it. Its main limitation is reliance on a single action verb across named domains and limited natural-term variation beyond the brand name.

DimensionReasoningScore

Specificity

Names four concrete Tamagui domains ('config v4, compiler optimization, styled context, and cross-platform styling') but relies on a single action verb ('Provides patterns for'), so it names domains and some actions without being comprehensive.

2 / 3

Completeness

Explicitly answers both what ('Provides Tamagui patterns for…') and when ('Must use when working with Tamagui projects…'), with an explicit 'Must use when' trigger clause.

3 / 3

Trigger Term Quality

Includes relevant triggers a user would say ('Tamagui projects', 'tamagui.config.ts', '@tamagui imports') but offers few natural phrasing variations beyond the single brand name.

2 / 3

Distinctiveness Conflict Risk

'Tamagui' plus the concrete triggers 'tamagui.config.ts' and '@tamagui imports' carve a clear niche that is unlikely to fire for unrelated skills.

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
NeverSight/skills_feed
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.