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).

1.77x

Quality

80%

Does it follow best practices?

Impact

94%

1.77x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xbigboss/claude-code/tamagui-best-practices/SKILL.md

Quality

Content

72%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 highly actionable, code-rich reference that is concise and pattern-oriented, with strong progressive-disclosure signaling in the body. Its main weaknesses are the lack of explicit validation/workflow checkpoints and the fact that the referenced pattern files do not exist in the bundle.

Suggestions

Add a short verification step for compiler-optimization changes (e.g. run the Tamagui compiler/build and check for flatten output) so workflow_clarity can score above 3.

Create the referenced bundle files (@DIALOG_PATTERNS.md, @FORM_PATTERNS.md, @ANIMATION_PATTERNS.md, @OVERLAY_PATTERNS.md, @COMPILER_PATTERNS.md, @DESIGN_SYSTEM.md) or remove the references, since the mandatory-loading table points to files that are absent from the bundle.

Tighten the createThemes palette example and the shorthand/breakpoint tables to reduce inline bulk and push conciseness toward 5.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with executable code blocks and little padding of concepts Claude already knows, though a few inline tables and verbose sections (e.g. createThemes palette) could be trimmed, matching the 4 'minor over-explanation' anchor rather than the lean 5.	4 / 5
Actionability	Nearly every section provides copy-paste-ready, executable TSX/bash examples covering common cases (config setup, styled, styleable, accept, anti-patterns, doc-fetching commands), matching the fully-executable 5 anchor.	5 / 5
Workflow Clarity	Content is organized by topic rather than as a sequenced workflow, and there are no explicit validation/checkpoint steps; for the build/compiler-oriented and anti-pattern guidance this is acceptable but lacks the feedback loops the 4-5 anchors require.	3 / 5
Progressive Disclosure	The skill signals one-level-deep pattern files (@DIALOG_PATTERNS.md etc.) via a mandatory-loading table, but those referenced files are not present in the bundle; with references present but not verifiable and significant detail inlined, this sits at the 3 anchor.	3 / 5
	Total	15 / 20 Passed

Description

87%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, domain-specific description that clearly answers both what the skill does and when to use it, with concrete Tamagui-specific trigger terms. Minor gains are possible by broadening trigger-term synonyms, but it is well above midpoint across all dimensions.

Dimension	Reasoning	Score
Specificity	Names the domain (Tamagui) and several concrete capabilities ('config v4, compiler optimization, styled context, and cross-platform styling'), which is multiple specific actions with only minor coverage gaps, fitting the 4 anchor rather than a fully comprehensive 5.	4 / 5
Completeness	It explicitly states both what it does ('Provides Tamagui patterns for...') and when to use it ('Must use when working with Tamagui projects (tamagui.config.ts, @tamagui imports)'), matching the clear what-and-when-with-concrete-triggers anchor.	5 / 5
Trigger Term Quality	Includes natural triggers like 'tamagui.config.ts' and '@tamagui imports' plus 'Tamagui projects', giving good keyword coverage; it misses common synonyms/variations a user might say, so it does not reach the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	The Tamagui-specific niche with concrete file/extension triggers ('tamagui.config.ts', '@tamagui imports') makes it clearly distinct with minimal conflict risk against other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: NeverSight/skills_feed
Path: data/skills-md/0xbigboss/claude-code/tamagui-best-practices/SKILL.md
Commit: 2f57aec

Reviewed: about 22 hours 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.