ReactLynx best practices — dual-thread React on Lynx
Write, review and refactor ReactLynx code for the dual-thread runtime — writing/review/refactor modes, a heuristic helper scanner, and nine rule documents (background-only, lifecycle, events, main-thread scripts, library packaging, global props, code splitting, profiling, static JSX)
- What
- Write, review and refactor ReactLynx code for the dual-thread runtime — writing/review/refactor modes, a heuristic helper scanner, and nine rule documents (background-only, lifecycle, events, main-thread scripts, library packaging, global props, code splitting, profiling, static JSX)
- Cost
- Free
- Needs
- a ReactLynx project the agent can read and refactor — the skill is a review/refactor methodology with a helper scanner, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @lynx-community's ReactLynx best-practices skill: write, review and refactor code for ReactLynx, where React's programming model meets Lynx's dual-thread runtime. The agent first classifies the task (writing / review / refactor), inspects the code for thread-boundary markers (`lynx.getJSModule`, `NativeModules`, `runOnMainThread`, `runOnBackground`, `main-thread:*`, `'background only'`), optionally runs the bundled heuristic scanner (`ReactLynxWorkflow`), then applies nine rule documents: detect-background-only (critical), avoid-use-layout-effect (`useEffect` for background side effects, main-thread layout events for layout reads), proper-event-handlers, main-thread-scripts-guide (JSON-serializable captures, no nested MTS), component-library-packaging (type-erased dist ESM with preserved JSX), global-props-mode, code-splitting (lazy default exports + Suspense), performance-profiling (trace events, displayName), hoist-static-jsx. Refactor mode reports findings first, explains which fixes are mechanical vs judgment calls, and applies only scoped changes with auto-fixes as suggestions. Honest caveats: the bundled scanner is a lightweight heuristic — it never replaces reading the code and applying the rule docs; explicitly excludes vanilla Lynx PAPI, DevTool/CDP debugging and build config (sibling skills cover those). Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
ReactLynx best practices is a free Muse skill for writing, reviewing and refactoring ReactLynx code for the dual-thread runtime. It offers writing, review and refactor modes, a heuristic helper scanner, and nine rule documents covering background-only code, lifecycle, events, main-thread scripts and more. It helps teams keep dual-thread React code correct, fast and consistent.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 2e7124eStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a ReactLynx project the agent can read and refactor — the skill is a review/refactor methodology with a helper scanner, not software to install Install "ReactLynx best practices — dual-thread React on Lynx" for me. It gives my agent @lynx-community's ReactLynx workflow: classify the task (writing/review/refactor), inspect code for thread-boundary markers, run the bundled heuristic scanner (ReactLynxWorkflow) when source is available, and apply the nine rule documents (detect-background-only, avoid-use-layout-effect, proper-event-handlers, main-thread-scripts-guide, component-library-packaging, global-props-mode, code-splitting, performance-profiling, hoist-static-jsx) — with refactor mode reporting findings first and applying only scoped, reviewed changes. Apache-2.0-licensed. Repository: https://raw.githubusercontent.com/lynx-community/skills/2e7124e336388236f91e1864e1e9fae6594d4f4b/packages/skills/reactlynx-best-practices/SKILL.md Pinned version: install the code at commit 2e7124e336388236f91e1864e1e9fae6594d4f4b exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and the rules/ and scripts/ folders) from the repository path into a temporary folder 2. Safety check: review the SKILL.md, rules and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "reactlynx-best-practices". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at my ReactLynx code; nothing else — it's a review methodology). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 2e7124e · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.