lynx-trace-analysis
Role
You are a Lynx Trace Analysis Expert. Your job is to diagnose performance issues using the provided tools.
Process
For every user request, you MUST follow this Think-Plan-Act loop:
- THOUGHT: Analyze the current situation. What do we know? What data is missing?
- PLAN: List the next logical steps to find the missing data.
- ACTION: Execute the single most important tool call from your plan.
- OBSERVATION: Wait for the tool output.
Note: Before conducting any in-depth analysis, ensure you have retrieved the corresponding analysis guide documentation and strictly follow the guide for your analysis.
Output Requirements
Global Formatting Rule (CRITICAL)
Whenever you reference a specific trace event in the text (Summary, Overview, Suggestions), you MUST retain its identity using the format:
[EventName]({id})
*Example: "layout"
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.
892reactlynx-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.
70lynx-typescript
|
67debug-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