react-patterns

React 19 patterns including Server Components, Actions, Suspense, hooks, and component composition

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a high-quality, lean React 19 patterns reference with executable examples and clear organization. Its main gap is progressive disclosure: everything lives in one file rather than splitting advanced material into referenced sub-files.

Suggestions

Split the larger reference sections (e.g. Server Components, Server Actions, custom hooks) into referenced files like SERVER_COMPONENTS.md and signal them from a concise overview to improve progressive disclosure.

Keep the SKILL.md body as a short overview with one-level-deep links so the main file stays under the monolithic threshold.

Dimension	Reasoning	Score
Conciseness	The body is lean: each section is executable code plus a brief, React-19-specific note, with no padding explaining basic concepts Claude already knows.	3 / 3
Actionability	Examples are complete, executable, and copy-paste ready (e.g. useActionState, useOptimistic, Server Actions with revalidatePath/redirect), with concrete rules listed.	3 / 3
Workflow Clarity	This is a reference/patterns skill with no destructive or batch operations requiring validation; per the simple-skill allowance, its clearly organized sections satisfy workflow clarity.	3 / 3
Progressive Disclosure	It is a single monolithic file well over 50 lines with all content inline and no external references, so while well-sectioned, content that could be split stays inline.	2 / 3
	Total	11 / 12 Passed

Description

72%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinctive with good natural trigger terms, but it omits any explicit 'when to use' guidance, which limits its completeness. Adding a 'Use when...' clause would raise it to the top level.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building React 19 features involving Server Components, Actions, Suspense, or new hooks.'

Lead with action verbs (e.g. 'Implement React 19 patterns...') to convert the capability list into concrete actions for higher specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain ('React 19 patterns') and lists specific capabilities ('Server Components, Actions, Suspense, hooks, and component composition'), but uses no action verbs, so it names capabilities rather than concrete actions.	2 / 3
Completeness	It clearly states what the skill covers, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like 'React 19', 'Server Components', 'Suspense', and 'hooks' are natural keywords a developer would actually say when needing these patterns, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	'React 19 patterns' is a clear, well-scoped niche with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rohitg00/awesome-claude-code-toolkit
Path: skills/react-patterns/SKILL.md
Commit: ebdf1d5

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.