Query Firebase Performance data from BigQuery for screen rendering metrics. Runs cost-optimized queries for 30-day screen summaries and daily trends. TRIGGER when: user wants to fetch/refresh performance data, see screen metrics, find worst-performing screens, or run BigQuery queries for rendering data. SKIP if: user is asking about setup or configuration (use /perf-setup), asking to visualize existing data (use /perf-dashboard), or asking to fix a specific screen (use /perf-fix). Requires /perf-setup to have run first.
Generate an interactive local HTML dashboard from Firebase Performance query results. Shows worst-performing screens, highest-volume screens, and 30-day trends with Chart.js. TRIGGER when: user asks for a dashboard, visualization, chart, report, HTML output, "show me the results", or "open dashboard" after running /perf-query. SKIP if: user hasn't run /perf-query yet (no .perf/data/ exists), or if they're asking to fetch new data (use /perf-query) or fix a screen (use /perf-fix).
Detect Firebase/GCP configuration, validate BigQuery access, and prepare for performance data queries. TRIGGER when: user asks about app performance, screen rendering metrics, frozen frames, slow rendering, Firebase Performance, BigQuery setup, or performance monitoring for their Android/iOS/Flutter app.
Fix screen rendering jank, frozen frames, and slow rendering for specific screens in Android or iOS apps. ONLY invoke when the developer explicitly asks to fix or optimize rendering performance of a named screen. Do NOT invoke during general code review, refactoring, bug fixes, or feature development — even if you notice performance smells.