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.
87
81%
Does it follow best practices?
Impact
99%
1.43xAverage score across 3 eval scenarios
Passed
No known issues
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 strong skill description with excellent trigger terms and completeness. It clearly identifies its niche in React component architecture patterns and provides explicit guidance on when to use it. The main weakness is that the capabilities could be more concrete - it describes patterns and concepts rather than specific actions Claude will perform.
Suggestions
Add specific concrete actions like 'Refactor prop-heavy components into compound component patterns, implement context-based state sharing, convert callback props to render props'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (React composition patterns) and mentions some actions like 'refactoring components' and 'building flexible component libraries', but doesn't list multiple concrete specific actions - it's more about patterns and concepts than discrete operations. | 2 / 3 |
Completeness | Clearly answers both what ('React composition patterns that scale') and when ('Use when refactoring components with boolean prop proliferation...') with explicit triggers. The 'Triggers on' clause provides additional explicit guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms: 'refactoring components', 'boolean prop proliferation', 'component libraries', 'compound components', 'render props', 'context providers', 'component architecture' - these are terms React developers would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific React architecture terminology like 'compound components', 'render props', 'boolean prop proliferation' - these are niche enough to avoid conflicts with general React or JavaScript 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 skill excels at organization and token efficiency, providing a well-structured overview with clear navigation to detailed content. However, it lacks inline code examples that would make it immediately actionable, and the workflow for applying these patterns during actual refactoring tasks is not clearly sequenced.
Suggestions
Add at least one concrete before/after code example inline (e.g., for architecture-avoid-boolean-props) to demonstrate the pattern without requiring file navigation
Include a brief decision workflow: 'When you see X, apply Y pattern' with specific triggers and actions
Add a quick diagnostic checklist for identifying which pattern to apply when reviewing existing component code
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and bullet points to convey information without explaining basic React concepts Claude already knows. Every section serves a clear purpose. | 3 / 3 |
Actionability | While the skill provides clear rule names and file paths, it lacks concrete code examples in the main file. The actual executable guidance is deferred to external rule files rather than shown inline. | 2 / 3 |
Workflow Clarity | The 'When to Apply' section lists triggers but doesn't provide a clear sequence for how to apply these patterns during refactoring. No validation steps or decision tree for choosing between patterns. | 2 / 3 |
Progressive Disclosure | Excellent structure with a quick reference overview, clear one-level-deep references to rule files, and a pointer to the full compiled document. Navigation is well-signaled and organized. | 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
- secondsky/claude-skills
- Commit
90d6bd7
- 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.