chrome-performance
Use Chrome DevTools MCP for frontend performance work such as slow page loads, LCP, CLS, INP, Lighthouse regressions, scripting hotspots, or layout thrash. Trigger when the user asks for page speed analysis, Core Web Vitals debugging, trace-based investigation, or before-and-after performance verification.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- chrome-performance
- description
- Use Chrome DevTools MCP for frontend performance work such as slow page loads, LCP, CLS, INP, Lighthouse regressions, scripting hotspots, or layout thrash. Trigger when the user asks for page speed analysis, Core Web Vitals debugging, trace-based investigation, or before-and-after performance verification.
03 SKILL.md 正文
Use this skill when performance findings need evidence from Chrome instead of code inspection alone.
Default Flow
- Start from the exact URL and device profile that reproduces the problem.
- Record a baseline with
lighthouse_auditorperformance_start_traceandperformance_stop_trace. - Drill into the highest-signal issue first, then inspect network, DOM, or scripts only as needed.
- After code changes, rerun the same scenario and compare the results.
Tool Selection
lighthouse_auditfor quick page-level diagnostics and report output.performance_start_traceandperformance_stop_tracefor deeper timing analysis.performance_analyze_insightto drill into a specific DevTools insight.emulateto keep device, network, CPU, and viewport conditions consistent.
Working Rules
- Keep the scenario deterministic: one URL, one interaction path, one device profile.
- Save traces and reports to files when they are large.
- Treat LCP, CLS, and INP as user-path problems; connect each finding to the specific element, request, or script that caused it.
- Avoid mixing unrelated experiments in one trace.
Expected Output
Return the problem, the evidence, the likely cause, and the concrete code area to change before proposing fixes.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.