SKILLEMALL.ai

BC react-patterns

React 19 performance patterns and composition architecture for Vite + Cloudflare projects. 50+ rules ranked by impact — eliminating waterfalls, bundle optimisation, re-render prevention, composition over boolean props, server/client boundaries, and React 19 APIs. Use when writing, reviewing, or refactoring React components. Triggers: 'react patterns', 'react review', 'react performance', 'optimise components', 'react best practices', 'composition patterns', 'why is it slow', 'reduce re-renders', 'fix waterfall'.

jezweb/claude-skills Agent Skills author: jezweb 1 file body ≈ 2 183 tokens Open the sourcegithub.com↗ analyzed 7 h ago

React 19 performance patterns and composition architecture for Vite + Cloudflare projects.

As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorCloudflareSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
84
Run on models
none yet
Process rating
C
56/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: react-patterns (Lord1Egypt/RA-Skills)

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 56/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 1 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 6 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2183 tokens
    • low 10 top-level sections: this looks like several domains in one skill
    • low The response is described with custom markup (20 tags): a typed call is more reliable

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 517: enough signal without eating the budget
    • +4Structure: 11 headings
    • +3Step-by-step instructions: 6 items
    • +4Has examples (2 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.