react-patterns

React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Quality

Content

100%

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

The body is an exemplar patterns skill: lean, executable, and well-structured, with decision trees that act as clear workflows and clean one-level-deep cross-references to sibling skills and rules.

Dimension	Reasoning	Score
Conciseness	Dense and assumes Claude's competence — no 'what is a hook/React' primers — with every section delivering a concrete pattern and minimal prose, matching the 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	Provides many fully executable TSX blocks (Cart, ProductPage, AddToCartButton, useActionState form, useOptimistic, useDebounce) plus concrete decision trees and a tool-specific data-fetching matrix, all copy-paste ready.	3 / 3
Workflow Clarity	Decision trees (State Location, Data Fetching matrix) and RSC boundary rules give clear 'if X -> do Y' sequencing; as a patterns skill with no destructive/batch operations, the simple-skill allowance applies and the guidance is unambiguous.	3 / 3
Progressive Disclosure	Body is a concise overview with clearly signaled, one-level-deep pointers (rules/react/hooks.md, sibling skills, react-testing, accessibility) plus a dedicated 'Out of Scope (Pointer Sections)' routing block; no nested reference chains.	3 / 3
	Total	12 / 12 Passed

Description

85%

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, complete, and well-scoped, listing concrete pattern areas with an explicit 'Use when' trigger. Its main weakness is trigger-term breadth: a single generic activation phrase undersells the many natural ways users request React help.

Suggestions

Broaden the 'Use when' clause to surface natural trigger phrasings users actually say, e.g. 'Use when writing, reviewing, or debugging React/JSX/TSX components, hooks, or Next.js App Router / RSC code'.

Mention the concrete triggers already in the body (Next.js App Router, RSC, Server/Client Components) in the description so the skill surfaces for those queries too.

Dimension	Reasoning	Score
Specificity	Enumerates many concrete actions — 'hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly answers both what (enumerated patterns) and when ('Use when writing or reviewing React components') with an explicit trigger clause, matching the 'answers both what AND when' anchor.	3 / 3
Trigger Term Quality	Has relevant keywords ('React components', 'hooks', 'forms', 'data fetching') but the sole trigger phrase 'Use when writing or reviewing React components' misses common variations a user would naturally say (JSX/TSX, Next.js, RSC, 'review my component'), so coverage is incomplete rather than score-3 broad.	2 / 3
Distinctiveness Conflict Risk	Targets a clear React 18/19 patterns niche with distinct triggers, unlikely to fire for non-React work; matches the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 8 suspicious	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Commit: 754b8dd

Reviewed: 4 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.