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 with excellent trigger terms and clear 'when' guidance tied to specific file patterns and imports. Its main weakness is that the 'what' portion lists topic areas rather than concrete actions, which slightly reduces specificity. Overall, it would perform well in a multi-skill selection scenario due to its distinct triggers.
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)'). The explicit trigger clause with file and import patterns is well-defined. | 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 would naturally mention when working with Tamagui. | 3 / 3 |
Distinctiveness Conflict Risk | Tamagui is a specific framework with distinct file patterns (tamagui.config.ts, @tamagui imports), making this highly unlikely to conflict with other skills. The niche is clearly defined and the triggers are unique to this framework. | 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 excellent progressive disclosure through its pattern file routing table. The code examples are concrete and executable, covering config setup, compound components, and anti-patterns. It could be tightened by removing basic React knowledge (inline functions, stable references) and adding validation steps for config/compiler workflows.
Suggestions
Remove the 'Inline Functions' anti-pattern section — this is basic React knowledge Claude already has and wastes tokens.
Add a validation step after config setup, e.g., 'Verify config loads: check that `npx tamagui doctor` passes' or similar compiler/build verification.
Move the Quick Reference tables (shorthands, breakpoints, animation drivers) and curl commands to a separate REFERENCE.md file to reduce main file length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good code examples, but includes some unnecessary explanations (e.g., the inline functions anti-pattern is basic React knowledge Claude already knows, and the 'Wrong Import Paths' section explains obvious differences). The quick reference tables and curl commands add bulk that could live in referenced files. | 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 all include concrete TSX code. The examples are complete and specific. | 3 / 3 |
Workflow Clarity | The 'Mandatory Context Loading' table provides a clear routing workflow for which file to read, and the compound component section has numbered steps. However, there are no validation checkpoints — no guidance on how to verify config is correct, no compiler validation steps, and no error recovery patterns for the multi-step config/theming setup. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear mandatory context loading table at the top routing to 6 specific pattern files (DIALOG_PATTERNS.md, FORM_PATTERNS.md, etc.), all one level deep. The main file serves as an overview with quick-start patterns 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
e437c3c
- 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.