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).
86
81%
Does it follow best practices?
Impact
94%
1.77xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its niche (Tamagui framework) with explicit trigger conditions including file patterns and import paths. Its main weakness is that the capabilities are described more as topic areas rather than concrete actions, which slightly reduces specificity. Overall, it would perform well in skill selection among many candidates.
Suggestions
Replace topic-area language with concrete actions, e.g., 'Configures Tamagui v4 themes and tokens, optimizes compiler settings, creates styled components with context, and implements cross-platform responsive layouts.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Tamagui) and mentions several specific areas like 'config v4', 'compiler optimization', 'styled context', and 'cross-platform styling', but these are more like topic areas than concrete actions. It doesn't list specific actions like 'configure themes', 'set up animations', or 'create styled components'. | 2 / 3 |
Completeness | Clearly answers both 'what' (provides Tamagui patterns for config v4, compiler optimization, styled context, cross-platform styling) and 'when' ('Must use when working with Tamagui projects (tamagui.config.ts, @tamagui imports)') with explicit file and import triggers. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'Tamagui', 'tamagui.config.ts', '@tamagui imports', 'cross-platform styling', 'compiler optimization', and 'styled context'. These cover both file-based triggers and conceptual terms a user working with Tamagui would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — Tamagui is a specific framework, and the description includes unique identifiers like 'tamagui.config.ts' and '@tamagui imports' that are unlikely to conflict with other styling or UI framework skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured Tamagui skill with strong actionability and progressive disclosure. The code examples are concrete and executable, covering config v4, compound components, styleable patterns, and common anti-patterns. The main weaknesses are moderate verbosity in some sections (curl commands, reference tables that could be in separate files) and lack of validation/verification steps for the multi-step processes described.
Suggestions
Move the 'Quick Reference' tables (shorthands, breakpoints, animation drivers) and 'Fetching Current Documentation' curl commands to a separate reference file to reduce token usage in the main SKILL.md.
Add validation checkpoints to the compound component workflow, e.g., 'Verify context propagation by checking that child components receive variant values' or 'If TypeScript errors appear on variants, ensure `as const` is applied.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with concrete code examples, but includes some unnecessary explanation (e.g., the intro paragraph restating the description, the 'Fetching Current Documentation' section with curl commands Claude likely knows how to construct, and the shorthands/breakpoints reference tables that could live in a separate file). Some anti-pattern explanations are slightly verbose but earn their place by showing correct alternatives. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples throughout — config setup, createThemes, compound components with createStyledContext, styleable patterns, accept prop usage, and anti-patterns with correct alternatives. Every pattern includes concrete TSX code that can be directly used. | 3 / 3 |
Workflow Clarity | The mandatory context loading table at the top provides clear sequencing for which files to read before coding. The compound component section has a clear numbered 4-step process. However, there are no validation checkpoints — no guidance on how to verify config is correct, no compiler validation steps, and no feedback loops for when things go wrong with styled context or compiler optimization. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure: the main SKILL.md serves as an overview with quick-start patterns and anti-patterns, while clearly referencing six separate pattern files (DIALOG_PATTERNS.md, FORM_PATTERNS.md, ANIMATION_PATTERNS.md, OVERLAY_PATTERNS.md, COMPILER_PATTERNS.md, DESIGN_SYSTEM.md) via a well-organized table at the top and a summary list at the bottom. All references are one level deep and clearly signaled. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
aa009ea
- 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.