trace-audit
Chrome DevTools Trace Audit
Analyze a Chrome DevTools Performance trace and produce a comprehensive performance audit report.
Usage
/trace-audit <path-to-trace.json>
The argument is the absolute path to a Chrome DevTools trace JSON file (exported from the Performance panel).
Workflow
Follow these steps in order. Use parallel tool calls wherever noted.
Step 1 — Validate the trace file
More from joyco-studio/skills
pr-description-writer
>
37parallel-claudes
>
32markdown-content
>
31joyco-lab
Use this skill whenever the user wants to isolate a piece of code, animation, or 3D experiment into a standalone JOYCO Lab experiment and publish it. Triggers include: \"isolate this\", \"publish this to the lab\", \"create a lab experiment\", \"extract this animation/effect/scene\", \"submit to JOYCO lab\", \"make this an experiment\". Also trigger when the user shows you a self-contained visual effect, animation, 3D scene, canvas sketch, or interactive component and wants to share or showcase it. Even if they don't say \"lab\" explicitly — if there's isolatable creative/technical code and a desire to share it, use this skill.
21thrash-report-analyzer
>
12webaudio
>
5