Analyze and optimize React component performance issues (slow renders, re-render thrash, laggy lists, expensive computations). Use when asked to profile or improve a React component, reduce re-renders, or speed up UI updates in React apps.
Install with Tessl CLI
npx tessl i github:Dimillian/Skills --skill react-component-performance89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Isolate ticking state from list
Timer extracted to child
100%
100%
Child component memoized
0%
100%
MessageRow memoized
100%
100%
useCallback for onDelete handler
100%
100%
Stable key used
100%
100%
Effect deps correct
100%
100%
UI behavior preserved
100%
100%
CHANGES.md documents problem
100%
100%
CHANGES.md documents fix
100%
100%
Without context: $0.1804 · 49s · 8 turns · 9 in / 2,612 out tokens
With context: $0.2220 · 58s · 11 turns · 59 in / 2,944 out tokens
Memoized derived data and stable keys
useMemo for filtered list
100%
100%
useMemo for category stats
100%
100%
useMemo for totalValue
100%
100%
useMemo for categories list
100%
100%
useCallback for handler
100%
100%
ProductRow memoized
100%
100%
Stable keys in product list
100%
100%
Stable keys in stats/options
100%
100%
CHANGES.md mentions inline computation
100%
100%
UI behavior preserved
100%
100%
Without context: $0.2078 · 45s · 9 turns · 10 in / 2,919 out tokens
With context: $0.5137 · 1m 47s · 23 turns · 270 in / 5,874 out tokens
Defer heavy rendering and effect hygiene
ArticleBody deferred
100%
100%
Effect has dependency array
100%
100%
ArticleCard memoized
0%
100%
onBookmark stabilized
0%
100%
Stable keys in list
100%
100%
Expanded state preserved
100%
100%
CHANGES.md: deferred rendering explained
100%
100%
CHANGES.md: effect issue explained
100%
100%
Without context: $0.2247 · 53s · 9 turns · 10 in / 3,469 out tokens
With context: $0.5103 · 1m 48s · 25 turns · 104 in / 6,299 out tokens
Table of Contents
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.