OpenHarmony React Native Performance Static Check Skills

Static-check rules and config for React Native for OpenHarmony, from the official performance-optimization doc. This skill is English-only to reduce token usage; Chinese content is available via links below.

When to Apply

Use this skill when:

• Writing or reviewing React Native for OpenHarmony (RNOH) application code or OpenHarmony project configuration
• Optimizing React Native page rendering, setState, or list performance
• Configuring bundle-harmony build, Hermes bytecode, or Release build
• Integrating or reviewing RNAbility lifecycle (onForeground/onBackground)
• Designing or implementing TurboModule (main vs worker thread)
• Preparing for performance analysis with Trace, React Marker, FCP, etc.

Rule Categories by Priority

Quick Reference

1. Render optimization (CRITICAL)

• rnoh-render-avoid-same-state — Avoid setState when state unchanged to prevent extra renders
• rnoh-render-pure-memo — Use PureComponent or React.memo to avoid unnecessary re-renders
• rnoh-render-props-once — Create callbacks/prop objects once (constructor or outside component)
• rnoh-render-split-child — Split independent UI into child components
• rnoh-render-merge-setstate — Merge setState to avoid multiple commits and renders
• rnoh-render-state-not-mutate — Use new objects in setState; do not mutate existing state
• rnoh-render-batching — Keep React 18 Automatic Batching enabled (RNOH default concurrentRoot: true)

2. Bundle & native config (HIGH)

• rnoh-bundle-release — Use --dev=false --minify=true for performance/production bundle
• rnoh-bundle-hbc — Prefer Hermes bytecode (hermesc) for production
• rnoh-native-release — Use Release build on native side; lower LOG_VERBOSITY_LEVEL when appropriate
• rnoh-native-bisheng — Optionally use BiSheng compiler (buildOption.nativeCompiler: "BiSheng")

3. Lifecycle & monitoring (HIGH)

• rnoh-lifecycle-foreground-background — Call onForeground/onBackground in onPageShow/onPageHide or onShown/onHidden
• rnoh-lifecycle-fcp — First-frame monitoring: use mount event or root onLayout to report FCP

4.