gaia-react-perf
SkillMediaDiagnose React render performance by driving a micro-interaction, capturing real renders, and surfacing memo-defeating reference instability with a recommended structural fix. Measure-only: it emits a diagnosis, it does not auto-fix. Trigger on `/gaia-react-perf` or natural-language asks like "profile renders", "measure renders", "why is X re-rendering", or "diagnose render performance". Do NOT trigger on vague "feels slow", "janky", or "optimize my app".
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the gaia-react-perf skill
What this skill tells your AI
The instructions your AI receives, as published by gaia-react/gaia in .claude/skills/gaia-react-perf/SKILL.md and read by ahel’s review.
Run the GAIA react-perf measure-only diagnostic with these arguments: $ARGUMENTS
Pre-flight: Worktree check
This skill drives the app's dev server and profiles the clone's build. If invoked from a linked worktree, reject hard: gaia_refuse_if_worktree (.gaia/scripts/main-only-lib.sh) asks the shared resolver which tree this is and refuses out loud, naming the main checkout, when the answer is a worktree.
Detection (run this first, before anything else):
. .gaia/scripts/main-only-lib.sh
gaia_refuse_if_worktree "/gaia-react-perf" || exit 1
If the detection does not fire, fall through to the workflow dispatch line below.
Read .claude/skills/gaia-react-perf/references/measure-only.md from the project root and follow it exactly. Treat the arguments above as an optional inline target (the page plus the micro-interaction to profile); if empty, ask the user to name a concrete micro-interaction before proceeding, per the reference.
Signals
- GitHub stars
- 23
- Forks
- 4
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
gaia-react-perf- Source
- github.com/gaia-react/gaia