React Rendering and Performance
Identify the actual cause of slow React interactions and reduce unnecessary work using measured state boundaries, subscriptions, scheduling and justified memoization.
9 CANONICAL SKILLS · V0.1.0
Profile real interactions, control browser concurrency and storage, preserve failure evidence and verify behavior before claiming an improvement.
Run from a full toolkit checkout. This prints a file manifest, not an installer.
node tools/bundle.mjs resolve frontend-performanceExplore the frontend worked guide →
Identify the actual cause of slow React interactions and reduce unnecessary work using measured state boundaries, subscriptions, scheduling and justified memoization.
Move suitable CPU-heavy work away from urgent UI interactions while controlling worker ownership, message identity, cancellation and stale results.
Set and evaluate route-specific frontend budgets for transfer size, main-thread work and user-visible loading without equating synthetic checks with field performance.
Persist frontend state only under explicit privacy, schema, quota and reconciliation policies; distinguish local durability from synchronized server acceptance.
Design initial, empty, refreshing, partially failed and mutation-pending UI states that preserve useful data and offer safe, attributable recovery.
Choose unit, component and browser checks around user-visible frontend contracts, with independent network fixtures and explicit integration coverage.
Use reproducible visual evidence to detect frontend regressions while preserving independent interaction, accessibility and content checks.
Keep untrusted content, navigation, credentials and server effects behind explicit boundaries while testing the real browser-to-server trust model.
Restructure React components, hooks and data flow while preserving user-visible behavior, state lifetime, focus and effect ownership.
Pick the skill needed for the current task. A private adapter supplies project-specific roots, command IDs, accepted contracts, and policy. It should pin and verify the public revision before exposing guidance to an internal agent.
Skill effectiveness remains experimental. Package validation and content hashes do not establish host compatibility, artifact authenticity, or permission to execute.
Read the private-adapter boundary ↗