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 tied to specific files and imports. The 'when' clause is strong with concrete signals. The main weakness is that the 'what' portion lists topic areas rather than specific concrete actions, making it slightly less actionable than ideal.
Suggestions
Replace 'Provides Tamagui patterns for' with more specific action verbs, e.g., 'Configures Tamagui v4 themes and tokens, optimizes compiler settings, creates styled components with context, and implements cross-platform styles.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Tamagui) and mentions several specific areas (config v4, compiler optimization, styled context, cross-platform styling), but these are more like topic areas than concrete actions. 'Provides patterns' is somewhat vague compared to listing specific actions like 'configure themes, optimize bundle size, 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)'). The explicit 'Must use when' clause with concrete file/import triggers satisfies the completeness requirement. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'Tamagui', 'tamagui.config.ts', '@tamagui imports', 'cross-platform styling', 'compiler optimization', 'styled context', and 'config v4'. These cover both file-based triggers and conceptual terms a user would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Tamagui is a specific framework with distinct file patterns (tamagui.config.ts, @tamagui imports), making this highly distinguishable from other styling or UI skills. Very unlikely to conflict with generic CSS, React Native, or other 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 strong skill file that provides highly actionable Tamagui patterns with executable code examples and excellent progressive disclosure through well-organized references to sub-pattern files. The main weaknesses are some unnecessary verbosity (explaining basic React concepts like stable callback references) and lack of validation checkpoints in multi-step workflows like config setup and compound component creation.
Suggestions
Remove the inline functions anti-pattern section — Claude already knows about useCallback and stable references; this wastes tokens on basic React knowledge.
Add a validation step after config setup (e.g., 'Verify config loads: check that `npx tamagui doctor` passes or that the dev server starts without errors').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good code examples, but includes some unnecessary explanations (e.g., the intro paragraph restating what the skill does, the 'Important' notes that could be tighter, and the inline functions anti-pattern which is basic React knowledge Claude already knows). | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples throughout — config setup, createThemes, compound components with createStyledContext, styleable(), accept prop, and anti-patterns all include concrete TSX code with clear usage examples. | 3 / 3 |
Workflow Clarity | The mandatory context loading table provides a clear workflow for which files to read before coding, and the compound component section has numbered steps. However, there are no validation checkpoints or feedback loops for the config setup or component creation processes, which involve multi-step operations that could fail silently. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear mandatory context loading table at the top pointing to six separate pattern files (DIALOG_PATTERNS.md, FORM_PATTERNS.md, etc.), all one level deep. The main file serves as an overview with quick-start content while deferring detailed topics to dedicated files. | 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
f772de4
- 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.