Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Static-check rules for React Native on OpenHarmony (RNOH), derived from the official ohos_react_native performance-optimization documentation. Covers render optimization, bundle configuration, RNAbility lifecycle, TurboModule threading, and list performance. Rules are categorized by priority from critical render issues to medium-impact list handling.
General React Native performance guides don't cover OpenHarmony-specific concerns like bundle-harmony, HBC compilation, BiSheng compiler options, or RNAbility lifecycle, so this skill fills that gap without requiring manual doc lookup.
When to use it
- Reviewing RNOH code for unnecessary re-renders before a release
- Configuring Hermes bytecode and Release builds for a production bundle
- Auditing TurboModule implementations to ensure heavy work runs on worker threads
- Checking RNAbility lifecycle hooks are wired to onPageShow/onPageHide correctly
- Enforcing stable list keys across a team codebase via code review rules
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: review this RNOH component for performance issues
- 1Check for setState calls where new value equals current state (rnoh-render-avoid-same-state)
- 2Check if functional components or class components lack React.memo or PureComponent (rnoh-render-pure-memo)
- 3Check if callbacks or prop objects are recreated on each render instead of being stable references (rnoh-render-props-once)
- 4Check if multiple setState calls could be merged into one (rnoh-render-merge-setstate)
- 5Check list items for missing or index-based keys (rnoh-list-key)
Annotated list of rule violations with rule IDs and fix suggestions