/web-quality-audit
Comprehensive web quality audit covering performance, accessibility, SEO, and best practices in a single review. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website" across multiple areas at once.
$ npx -y skills add tech-leads-club/agent-skills --skill web-quality-audit --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/web-quality-audit
Context preview
The summary Claude sees to decide when to auto-load this skill.
Comprehensive web quality audit covering performance, accessibility, SEO, and best practices in a single review. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website" across multiple areas at once.
SKILL.md
web-quality-audit.SKILL.mdname: web-quality-audit
description: Comprehensive web quality audit covering performance, accessibility, SEO, and best practices in a single review. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website" across multiple areas at once. Orchestrates specialized skills for depth. Do NOT use for single-area audits — prefer core-web-vitals, web-accessibility, seo, or web-best-practices for focused work.
license: MIT
metadata:
author: web-quality-skills
version: '1.0'
Web quality audit
Comprehensive quality review based on Google Lighthouse audits. Covers Performance, Accessibility, SEO, and Best Practices across 150+ checks.
How it works
1. Analyze the provided code/project for quality issues 2. Categorize findings by severity (Critical, High, Medium, Low) 3. Provide specific, actionable recommendations 4. Include code examples for fixes
Audit categories
Performance (40% of typical issues)
**Core Web Vitals** — Must pass for good page experience:
- **LCP (Largest Contentful Paint) < 2.5s.** The largest visible element must render quickly. Optimize images, fonts, and server response time.
- **INP (Interaction to Next Paint) < 200ms.** User interactions must feel instant. Reduce JavaScript execution time and break up long tasks.
- **CLS (Cumulative Layout Shift) < 0.1.** Content must not jump around. Set explicit dimensions on images, embeds, and ads.
**Resource Optimization:**
- **Compress images.** Use WebP/AVIF with fallbacks. Serve correctly sized images via `srcset`.
- **Minimize JavaScript.** Remove unused code. Use code splitting. Defer non-critical scripts.
- **Optimize CSS.** Extract critical CSS. Remove unused styles. Avoid `@import`.
- **Efficient fonts.** Use `font-display: swap`. Preload critical fonts. Subset to needed characters.
**Loading Strategy:**
- **Preconnect to origins.** Add `<link rel="preconnect">` for third-party domains.
- **Preload critical assets.** LCP images, fonts, and above-fold CSS.
- **Lazy load below-fold content.** Images, iframes, and heavy components.
- **Cache effectively.** Long cache TTLs for static assets. Immutable caching for hashed files.
Accessibility (30% of typical issues)
**Perceivable:**
- **Text alternatives.** Every `<img>` has meaningful `alt` text. Decorative images use `alt=""`.
- **Color contrast.** Minimum 4.5:1 for normal text, 3:1 for large text (WCAG AA).
- **Don't rely on color alone.** Use icons, patterns, or text alongside color indicators.
- **Captions and transcripts.** Video has captions. Audio has transcripts.
**Operable:**
- **Keyboard accessible.** All functionality available via keyboard. No keyboard traps.
- **Focus visible.** Clear focus indicators on all interactive elements.
- **Skip links.** Provide "Skip to main content" for keyboard users.
- **Sufficient time.** Users can extend time limits. No auto-advancing content without controls.
**Understandable:**
- **Page language.** Set `lang` attribute on `<html>`.
- **Consistent navigation.** Same navigation structure across pages.
- **Error identification.** Form errors clearly described and associated with fields.
- **Labels and instructions.** All form inputs have associated labels.
**Robust:**
- **Valid HTML.** No duplicate IDs. Properly nested elements.
- **ARIA used correctly.** Prefer native elements. ARIA roles match behavior.
- **Name, role, value.** Interactive elements have accessible names and correct roles.
SEO (15% of typical issues)
**Crawlability:**
- **Valid robots.txt.** Doesn't block important resources.
- **XML sitemap.** Lists all important pages. Submitted to Search Console.
- **Canonical URLs.** Prevent duplicate content issues.
- **No noindex on important pages.** Check meta robots and headers.
**On-Page SEO:**
- **Unique title tags.** 50-60 characters. Primary keyword included.
- **Meta descriptions.** 150-160 characters. Compelling and unique.
- **Heading hierarchy.** Single `<h1>`. Logical heading structure.
- **Descriptive link text.** Not "click here" or "read more".
**Technical SEO:**
- **Mobile-friendly.** Responsive design. Tap targets ≥ 48px.
- **HTTPS.** Secure connection required.
- **Fast loading.** Performance directly impacts ranking.
- **Structured data.** JSON-LD for rich snippets (Article, Product, FAQ, etc.).
Best practices (15% of typical issues)
**Security:**
- **HTTPS everywhere.** No mixed content. HSTS enabled.
- **No vulnerable libraries.** Keep dependencies updated.
- **CSP headers.** Content Security Policy to prevent XSS.
- **No exposed source maps.** In production builds.
**Modern Standards:**
- **No deprecated APIs.** Replace `document.write`, synchronous XHR, etc.
- **Valid doctype.** Use `<!DOCTYPE html>`.
- **Charset declared.** `<meta charset="UTF-8">` as first element in `<head>`.
- **No browser errors.** Clean console. No CORS issues.
**UX Patterns:**
- **No intrusive interstitials.** Especially on mobile.
- **Clear permission requests.** Only ask when needed, with context.
- **No misleading buttons.** Buttons do what they say.
Severity levels
| Level | Description | Action | | ------------ | --------------------------------------------- | ------------------- | | **Critical** | Security vulnerabilities, complete failures | Fix immediately | | **High** | Core Web Vitals failures, major a11y barriers | Fix before launch | | **Medium** | Performance opportunities, SEO improvements | Fix within sprint | | **Low** | Minor optimizations, code quality | Fix when convenient |
Audit output format
When performing an audit, structure findings as:
## Audit results
### Critical issues (X found)
- **[Category]** Issue description. File: `path/to/file.js:123`
- **Impact:** Why this matters
- **Fix:** Specific code change or recommendation
### High priority (X found)
...
Read more
name: web-quality-audit description: Comprehensive web quality audit covering performance, accessibility, SEO, and best practices in a single review. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website" across multiple areas at once. Orchestrates specialized skills for depth. Do NOT use for single-area audits — prefer core-web-vitals, web-accessibility, seo, or web-best-practices for focused work. license: MIT metadata: author: web-quality-skills version: '1.0'
Web quality audit
Comprehensive quality review based on Google Lighthouse audits. Covers Performance, Accessibility, SEO, and Best Practices across 150+ checks.
How it works
1. Analyze the provided code/project for quality issues 2. Categorize findings by severity (Critical, High, Medium, Low) 3. Provide specific, actionable recommendations 4. Include code examples for fixes
Audit categories
Performance (40% of typical issues)
**Core Web Vitals** — Must pass for good page experience:
- **LCP (Largest Contentful Paint) < 2.5s.** The largest visible element must render quickly. Optimize images, fonts, and server response time.
- **INP (Interaction to Next Paint) < 200ms.** User interactions must feel instant. Reduce JavaScript execution time and break up long tasks.
- **CLS (Cumulative Layout Shift) < 0.1.** Content must not jump around. Set explicit dimensions on images, embeds, and ads.
**Resource Optimization:**
- **Compress images.** Use WebP/AVIF with fallbacks. Serve correctly sized images via `srcset`.
- **Minimize JavaScript.** Remove unused code. Use code splitting. Defer non-critical scripts.
- **Optimize CSS.** Extract critical CSS. Remove unused styles. Avoid `@import`.
- **Efficient fonts.** Use `font-display: swap`. Preload critical fonts. Subset to needed characters.
**Loading Strategy:**
- **Preconnect to origins.** Add `<link rel="preconnect">` for third-party domains.
- **Preload critical assets.** LCP images, fonts, and above-fold CSS.
- **Lazy load below-fold content.** Images, iframes, and heavy components.
- **Cache effectively.** Long cache TTLs for static assets. Immutable caching for hashed files.
Accessibility (30% of typical issues)
**Perceivable:**
- **Text alternatives.** Every `<img>` has meaningful `alt` text. Decorative images use `alt=""`.
- **Color contrast.** Minimum 4.5:1 for normal text, 3:1 for large text (WCAG AA).
- **Don't rely on color alone.** Use icons, patterns, or text alongside color indicators.
- **Captions and transcripts.** Video has captions. Audio has transcripts.
**Operable:**
- **Keyboard accessible.** All functionality available via keyboard. No keyboard traps.
- **Focus visible.** Clear focus indicators on all interactive elements.
- **Skip links.** Provide "Skip to main content" for keyboard users.
- **Sufficient time.** Users can extend time limits. No auto-advancing content without controls.
**Understandable:**
- **Page language.** Set `lang` attribute on `<html>`.
- **Consistent navigation.** Same navigation structure across pages.
- **Error identification.** Form errors clearly described and associated with fields.
- **Labels and instructions.** All form inputs have associated labels.
**Robust:**
- **Valid HTML.** No duplicate IDs. Properly nested elements.
- **ARIA used correctly.** Prefer native elements. ARIA roles match behavior.
- **Name, role, value.** Interactive elements have accessible names and correct roles.
SEO (15% of typical issues)
**Crawlability:**
- **Valid robots.txt.** Doesn't block important resources.
- **XML sitemap.** Lists all important pages. Submitted to Search Console.
- **Canonical URLs.** Prevent duplicate content issues.
- **No noindex on important pages.** Check meta robots and headers.
**On-Page SEO:**
- **Unique title tags.** 50-60 characters. Primary keyword included.
- **Meta descriptions.** 150-160 characters. Compelling and unique.
- **Heading hierarchy.** Single `<h1>`. Logical heading structure.
- **Descriptive link text.** Not "click here" or "read more".
**Technical SEO:**
- **Mobile-friendly.** Responsive design. Tap targets ≥ 48px.
- **HTTPS.** Secure connection required.
- **Fast loading.** Performance directly impacts ranking.
- **Structured data.** JSON-LD for rich snippets (Article, Product, FAQ, etc.).
Best practices (15% of typical issues)
**Security:**
- **HTTPS everywhere.** No mixed content. HSTS enabled.
- **No vulnerable libraries.** Keep dependencies updated.
- **CSP headers.** Content Security Policy to prevent XSS.
- **No exposed source maps.** In production builds.
**Modern Standards:**
- **No deprecated APIs.** Replace `document.write`, synchronous XHR, etc.
- **Valid doctype.** Use `<!DOCTYPE html>`.
- **Charset declared.** `<meta charset="UTF-8">` as first element in `<head>`.
- **No browser errors.** Clean console. No CORS issues.
**UX Patterns:**
- **No intrusive interstitials.** Especially on mobile.
- **Clear permission requests.** Only ask when needed, with context.
- **No misleading buttons.** Buttons do what they say.
Severity levels
| Level | Description | Action | | ------------ | --------------------------------------------- | ------------------- | | **Critical** | Security vulnerabilities, complete failures | Fix immediately | | **High** | Core Web Vitals failures, major a11y barriers | Fix before launch | | **Medium** | Performance opportunities, SEO improvements | Fix within sprint | | **Low** | Minor optimizations, code quality | Fix when convenient |
Audit output format
When performing an audit, structure findings as:
## Audit results ### Critical issues (X found) - **[Category]** Issue description. File: `path/to/file.js:123` - **Impact:** Why this matters - **Fix:** Specific code change or recommendation ### High priority (X found) ...
The secure, validated skill registry for professional AI coding agents. Extend Antigravity, Claude Code, Cursor, Copilot and more with absolute confidence.
Repo: tech-leads-club/agent-skills
Other skills on tech-leads-club-agent-skills.
- /component-common-domain-detection
Finds duplicate business logic spread across multiple components and suggests consolidation. Use when asking "where is this logic duplicated?", "find common code between services", "what can be consolidated?", "detect shared domain logic", or analyzing component overlap before
Open skill - /component-flattening-analysis
Detects misplaced classes and fixes component hierarchy problems — finds code that should belong inside a component but sits at the root level. Use when asking "clean up component structure", "find orphaned classes", "fix module hierarchy", "flatten nested components", or
Open skill - /component-identification-sizing
Maps architectural components in a codebase and measures their size to identify what should be extracted first. Use when asking "how big is each module?", "what components do I have?", "which service is too large?", "analyze codebase structure", "size my monolith", or planning
Open skill - /coupling-analysis
Analyzes coupling between modules using the three-dimensional model (strength, distance, volatility) from "Balancing Coupling in Software Design". Use when asking "are these modules too coupled?", "show me dependencies", "analyze integration quality", "which modules should I
Open skill - /decomposition-planning-roadmap
Creates step-by-step decomposition plans and migration roadmaps for breaking apart monolithic applications. Use when asking "what order should I extract services?", "plan my migration", "create a decomposition roadmap", "prioritize what to split", "monolith to microservices
Open skill - /domain-analysis
Maps business domains and suggests service boundaries in any codebase using DDD Strategic Design. Use when asking "what are the domains in this codebase?", "where should I draw service boundaries?", "identify bounded contexts", "classify subdomains", "DDD analysis", or analyzing
Open skill