core-web-vitals
When the user wants to optimize Core Web Vitals, fix LCP, INP, or CLS issues. Also use when the user mentions "Core Web Vitals," "CWV," "LCP," "INP," "CLS," "FID," "page speed," "page performance," "Largest Contentful Paint," "Interaction to Next Paint," "Cumulative Layout Shift," or "Page Experience." For GSC CWV, use google-search-console.
What this skill does
# SEO Technical: Core Web Vitals Guides optimization of Core Web Vitals (CWV)—Google's user experience metrics that affect search ranking. CWV are confirmed ranking factors for mobile and desktop. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Scope (Technical SEO) - **LCP** (Largest Contentful Paint): Loading performance; time to render largest content element - **INP** (Interaction to Next Paint): Responsiveness; replaced FID on March 12, 2024 - **CLS** (Cumulative Layout Shift): Visual stability; unexpected layout shifts ## Target Thresholds (75th percentile, field data) | Metric | Target | Good | Needs Improvement | Poor | |--------|--------|------|-------------------|------| | **LCP** | ≤2.5s | ≤2.5s | 2.5–4.0s | >4.0s | | **INP** | ≤200ms | ≤200ms | 200–500ms | >500ms | | **CLS** | <0.1 | ≤0.1 | 0.1–0.25 | >0.25 | **Source**: [Google Page Experience](https://developers.google.com/search/docs/appearance/page-experience) ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for site URL. Identify: 1. **Tools**: GSC Core Web Vitals report, PageSpeed Insights, Chrome DevTools 2. **Metrics**: Which metric is failing (LCP, INP, CLS) 3. **Page type**: Hero, article, product, list—LCP candidate differs ## LCP Optimization LCP measures the time until the largest content element (image, video, or text block) is visible. | Cause | Fix | |-------|-----| | **Slow server response** | Reduce TTFB; use CDN; optimize server | | **Render-blocking resources** | Defer non-critical CSS/JS; inline critical CSS | | **Large images** | WebP/AVIF; compress; `width`/`height` to prevent CLS; see **image-optimization** | | **Client-side rendering** | SSR/SSG for above-fold content; see **rendering-strategies** | | **Third-party scripts** | Load async; defer non-critical | **LCP candidates**: Hero image, large text block, video poster. Ensure above-fold images use `loading="eager"` (default); never lazy-load LCP. ## INP Optimization INP measures responsiveness—time from user interaction to next paint. Replaced FID on March 12, 2024. | Cause | Fix | |-------|-----| | **Long-running JS** | Break tasks >50ms; use `requestIdleCallback`; Web Workers | | **Heavy event handlers** | Debounce/throttle; defer non-critical work | | **Main thread blocking** | Reduce third-party scripts; defer non-critical JS | | **Layout thrashing** | Batch DOM reads/writes; avoid forced reflows | ## CLS Optimization CLS measures unexpected layout shifts. | Cause | Fix | |-------|-----| | **Images without dimensions** | Always set `width` and `height` attributes | | **Dynamic content** | Reserve space for ads, embeds; use `min-height` | | **Web fonts** | `font-display: optional` or `swap`; preload critical fonts | | **Animations** | Use `transform` instead of `top`/`left`/`width` | **Reserve space**: For images, ads, embeds—define dimensions before load. Avoid inserting content above existing content without reserved space. ## Tools & Monitoring | Tool | Use | |------|-----| | **GSC** | Core Web Vitals report; URL grouping; field data | | **PageSpeed Insights** | Lab + field data; mobile + desktop | | **Chrome DevTools** | Performance panel; LCP element; layout shift overlay | ## Output Format - **Current state**: Which metrics fail (LCP, INP, CLS) - **Prioritized fixes**: By impact - **References**: [Web Vitals](https://web.dev/vitals/), [Page Experience](https://developers.google.com/search/docs/appearance/page-experience) ## Related Skills - **image-optimization**: LCP image optimization; WebP; lazy loading (below-fold only) - **google-search-console**: CWV report; field data monitoring - **mobile-friendly**: Mobile-first indexing; mobile CWV targets - **rendering-strategies**: SSR/SSG for LCP; content in initial HTML - **site-crawlability**: Redirect chains waste crawl; fix for performance
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.