ops-performance_skill

This skill analyzes Expo and serverless app performance, running Lighthouse audits, bundle size checks, and k6 load tests to optimize reliability.

TypeScript

1

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill codyswanngt/lisa --skill ops-performance

SKILL.md3.7 KB

Overview

This skill performs performance analysis for Expo frontend projects paired with serverless backends. It runs Lighthouse audits, bundle-size inspection, and k6 load tests to give actionable metrics and recommendations for web and API performance.

How this skill works

It discovers frontend and backend entry points by reading package.json scripts and environment constants, then runs Lighthouse either locally or against deployed URLs, exports a production build to analyze bundle composition, and executes k6 scenarios defined in the backend. Results are parsed into Lighthouse scores, Core Web Vitals, bundle breakdowns, and k6 throughput/latency/error metrics with tailored recommendations when thresholds are missed.

When to use it

Before a release to validate frontend Core Web Vitals and SEO metrics.
When bundle size growth needs investigation or tree-shaking verification.
During capacity planning or after changes to backend endpoints to verify performance under load.
When comparing local dev performance to deployed environments.
Regular CI checks to catch regressions in Lighthouse or load test results.

Best practices

Ensure BACKEND_DIR is set in .claude/settings.local.json when backend is not at ../backend-v2.
Commit or provide environment constants (e2e/constants.ts or .env.*) so deployed URLs are discoverable.
Run bun run export:web before bundle analysis to get accurate production artifacts.
Use LHCI (lighthouse:check) in CI to standardize Lighthouse runs and baseline comparisons.
Start with smoke k6 tests, then progress to load, stress, and spike to understand system behavior incrementally.

Example use cases

Run full analysis (all) to produce Lighthouse JSON, a bundle breakdown, and k6 load test summary for a release candidate.
Quickly check frontend bundle bloat by running export:web and listing largest JS files in dist/.
Verify Core Web Vitals locally with a headless Lighthouse run against http://localhost:8081.
Execute backend k6:load to validate average and p95 response times before traffic increases.
Use Docker-based k6 commands in CI to avoid local k6 installation requirements.

FAQ

The skill reads frontend package.json in the current directory and looks for BACKEND_DIR (default ../backend-v2) or package.json k6:* scripts in the backend directory.

What thresholds trigger recommendations?

Recommendations are suggested when Lighthouse category scores or Core Web Vitals exceed common thresholds (for example LCP > 2.5s, CLS > 0.1, TBT > 200ms) or when k6 p95 latency and error rates indicate service degradation.