Prompts Every React Developer Should Keep

A performance-review prompt that forces ranking by impact before any fix, which stops the usual memo-everything reflex. The minimal-fix constraint keeps diffs reviewable. Paste one component at a time for best results.

Turns the vaguest part of React — effects — into a table audit with a verdict per effect. The 'should this be an event handler' question catches the majority of real-world effect misuse. Great pre-review pass.

A debugging discipline in prompt form: hypotheses with evidence both ways and a cheapest-experiment step, with fixes explicitly forbidden until confirmation. Cuts wild-goose-chase time dramatically on unfamiliar codebases.

A refactoring prompt that puts characterisation tests before any code movement and outlaws behaviour changes — suspected bugs get flagged, not silently fixed. The output is a safe, reviewable migration rather than a rewrite gamble.