reactlynx-best-practices
ReactLynx Best Practices
ReactLynx best practices covering dual-thread architecture and React patterns. Provides rules reference for writing, static analysis for reviewing, and auto-fix for refactoring.
When to Apply
This skill should be used when:
- Writing new ReactLynx components or application → Reference rules as guidelines
- Reviewing existing ReactLynx code → Use scanner to detect issues
- Refactoring ReactLynx code → Use auto-fix with user approval
Input
This skill accepts the following inputs:
| Input | Required | Description |
|---|---|---|
sourceCode |
No | The ReactLynx source code to analyze (string or file path) |
mode |
No | Workflow mode: writing, review, or refactor. Auto-detected if not specified |
More from lynx-community/skills
lynx-devtool
Interact with Lynx DevTool to inspect and debug Lynx applications. Use this skill to list connected clients and sessions, send Chrome DevTools Protocol (CDP) commands, send App commands, and open URLs in Lynx. This is useful for debugging UI issues, inspecting runtime state, or automating interactions with Lynx apps.
862lynx-typescript
|
67lynx-trace-analysis
|
55debug-info-remapping
Remap the function_id:pc_index to the original source code position by provided debug info json file.
54lynx-trace-record
This guide provides step-by-step instructions for recording Lynx performance traces. Use this guide when the user asks how to record a trace.
53habitat-usage
Guidance on using Habitat to manage multi-repo source and asset dependencies via .habitat/DEPS and hab sync, plus troubleshooting common sync failures.
41