Comprehensive quality review based on Google Lighthouse audits. Covers Performance, Accessibility, SEO, and Best Practices across 150+ checks.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionweb-quality-auditExecute the skills CLI command in your project's root directory to begin installation:
Fetches web-quality-audit from davila7/claude-code-templates and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate web-quality-audit. Access via /web-quality-audit in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
24.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
24.2K
stars
Comprehensive quality review based on Google Lighthouse audits. Covers Performance, Accessibility, SEO, and Best Practices across 150+ checks.
Core Web Vitals — Must pass for good page experience:
Resource Optimization:
srcset.@import.font-display: swap. Preload critical fonts. Subset to needed characters.Loading Strategy:
<link rel="preconnect"> for third-party domains.Perceivable:
<img> has meaningful alt text. Decorative images use alt="".Operable:
Understandable:
lang attribute on <html>.Robust:
Crawlability:
On-Page SEO:
<h1>. Logical heading structure.Technical SEO:
Security:
Modern Standards:
document.write, synchronous XHR, etc.<!DOCTYPE html>.<meta charset="UTF-8"> as first element in <head>.UX Patterns:
| 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 |
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)
...
### Summary
- Performance: X issues (Y critical)
- Accessibility: X issues (Y critical)
- SEO: X issues
- Best Practices: X issues
### Recommended priority
1. First fix this because...
2. Then address...
3. Finally optimize...
For detailed guidelines on specific areas:
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
davila7/claude-code-templates
supercent-io/skills-template
shadcn/improve
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
Solid pick for teams standardizing on skills: web-quality-audit is focused, and the summary matches what you get after install.
web-quality-audit has been reliable in day-to-day use. Documentation quality is above average for community skills.
web-quality-audit is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend web-quality-audit for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: web-quality-audit is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: web-quality-audit is focused, and the summary matches what you get after install.
web-quality-audit has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in web-quality-audit — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
web-quality-audit is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
web-quality-audit reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 46