react-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture.
81
71%
Does it follow best practices?
Impact
99%
1.43xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/react-composition-patterns/skills/react-composition-patterns/SKILL.mdQuality
Discovery
100%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 an excellent skill description that clearly defines its niche in React composition patterns and component architecture. It provides specific concrete actions, natural trigger terms that developers would use, explicit 'Use when' and 'Triggers on' clauses, and is highly distinctive from other potential React-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and patterns: 'refactoring components with boolean prop proliferation', 'building flexible component libraries', 'designing reusable APIs', and names specific patterns like 'compound components, render props, context providers'. | 3 / 3 |
Completeness | Clearly answers both what ('React composition patterns that scale') and when ('Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture.'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'refactoring components', 'boolean prop proliferation', 'component libraries', 'compound components', 'render props', 'context providers', 'component architecture'. These are terms React developers naturally use when facing these problems. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — focuses specifically on React composition patterns and component architecture, with precise triggers like 'boolean prop proliferation', 'compound components', and 'render props' that clearly distinguish it from general React skills or styling skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions as a well-organized table of contents but lacks any substantive actionable content. It categorizes and references external rule files effectively, but provides zero concrete code examples or executable guidance within the skill itself. A developer or Claude reading only this file would know what patterns exist but not how to implement any of them.
Suggestions
Add at least one concrete before/after code example for the highest-priority pattern (architecture-avoid-boolean-props) showing boolean prop proliferation vs. compound component composition.
Include a brief decision workflow: 'When you see X, apply pattern Y' with specific code-level signals (e.g., 'If a component has 3+ boolean props controlling rendering, refactor using compound components').
Add a minimal executable example of the compound component pattern with context provider so the skill is useful without requiring external file reads.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary framing (e.g., 'These patterns make codebases easier for both humans and AI agents to work with as they scale') and the 'When to Apply' section largely restates the description. The priority table with prefix conventions adds marginal value. | 2 / 3 |
Actionability | No concrete code examples, no executable patterns, no specific commands. The skill is entirely a catalog/index pointing to other files without providing any actual implementation guidance. Claude would need to read external files to get any actionable content. | 1 / 3 |
Workflow Clarity | The skill provides a clear categorization and priority ordering of patterns, but there's no workflow for how to apply these patterns during a refactoring task—no sequence of steps, no validation checkpoints, no decision tree for choosing between patterns. | 2 / 3 |
Progressive Disclosure | Well-structured as an overview with clear one-level-deep references to individual rule files and a compiled AGENTS.md. Navigation is straightforward with the quick reference table linking to specific rule files. | 3 / 3 |
Total | 8 / 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
- secondsky/claude-skills
- Commit
88da5ff
- 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.