Audit Core Web Vitals and auto-fix what's dragging your score down
Clients want rich pages and fast load times. This recipe runs Lighthouse, identifies the biggest performance bottlenecks, and drafts the fixes most likely to improve Core Web Vitals before handoff.
Create a skill called "Lighthouse Mechanic". When I give you a website URL, run a Lighthouse performance audit. Identify the specific bottleneck for each Core Web Vital metric (LCP, CLS, INP, FCP, TTFB) — which element, script, or resource is the culprit. Then prepare fixes where possible: recommend lazy loading for below-fold images, add width/height attributes to images and embeds to prevent CLS, suggest font-display strategies and font subsetting, defer or async non-critical scripts, preload critical resources, and flag minification opportunities. Analyze the performance impact of each third-party script and recommend which to keep, lazy-load, or remove. Show a before/after comparison when changes can be tested. For issues that cannot be auto-drafted, provide specific code fixes with estimated score impact.
Give your Claw a staging or live URL, and it runs a full Lighthouse
performance audit, diagnoses the issues dragging down Core Web Vitals,
and prepares a prioritized fix plan. Where source files are available,
it can also draft implementation changes for review.
Compress, convert, and generate srcsets for every image in one pass
Images are half the weight of the average web page. This recipe takes a folder of images and outputs optimized WebP/AVIF versions at multiple breakpoint widths, with the responsive HTML picture elements ready to paste.
Subset, preload, and self-host web fonts without the FOUT
Font loading causes flash of unstyled text, layout shifts, and GDPR headaches with Google Fonts. This recipe takes your fonts, subsets them to only the characters you use, generates optimal loading strategies, and creates fallback fonts with matched metrics — eliminating CLS.
Turn finished projects into polished portfolio pieces without the 10-hour writing slog
Your portfolio is 3 years outdated because writing case studies takes longer than the projects themselves. This recipe takes your project files, Figma history, and a few bullet points from you, and drafts a complete case study — challenge, process, solution, results.
Auto-generate proxies the moment footage lands
Choppy playback, laggy scrubbing, and unusable timelines — even on strong machines — often comes down to editing long-GOP or heavy codecs at high resolution without proxies. This recipe generates proxies automatically whenever new camera originals appear, so every project starts edit-ready instead of debug-ready.