Optimize web performance through Core Web Vitals, modern browser APIs (View Transitions, Speculation Rules), and framework-specific techniques.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionweb-performance-optimizationExecute the skills CLI command in your project's root directory to begin installation:
Fetches web-performance-optimization from bobmatnyc/claude-mpm-skills 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-performance-optimization. Access via /web-performance-optimization 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
29
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
29
stars
Optimize web performance through Core Web Vitals, modern browser APIs (View Transitions, Speculation Rules), and framework-specific techniques.
Business Impact: 1 second delay = 7% conversion loss. 0.1s improvement = 8% increase in conversions.
High-ROI optimizations by time investment:
1 Hour Quick Wins (⭐⭐⭐⭐⭐ ROI):
loading="lazy" to below-fold images (40-60% weight reduction)rel="preconnect" for critical origins (100-500ms savings)1 Day Investments (⭐⭐⭐⭐ ROI):
fetchpriority="high" (200-400ms improvement)1 Week Comprehensive (⭐⭐⭐⭐⭐ ROI):
→ See quick-wins.md for complete implementation details
| Metric | Target | Weight | Key Optimization |
|---|---|---|---|
| LCP (Largest Contentful Paint) | <2.5s | 25% | Optimize images, preload critical resources |
| INP (Interaction to Next Paint) | <200ms | 30% | Reduce JavaScript, break up long tasks |
| CLS (Cumulative Layout Shift) | <0.1 | 25% | Reserve space, optimize fonts |
| TBT (Total Blocking Time) | <200ms | 30% | Code splitting, defer non-critical JS |
| FCP (First Contentful Paint) | <1.8s | 10% | Eliminate render-blocking resources |
→ See core-web-vitals.md for deep dive on each metric
View Transitions API - Smooth page transitions without JavaScript
@view-transition { navigation: auto; }
Speculation Rules API - Prerender pages for instant navigation
React Server Components - Zero-bundle server components
Priority Hints - fetchpriority="high" for LCP optimization
Content Visibility - CSS-based rendering optimization
→ See modern-patterns-2025.md for cutting-edge techniques
Stop and reconsider if:
Conversion Impact:
SEO Impact:
Remember: Performance is a feature, not an afterthought. Every millisecond counts. Start with Quick Wins for immediate impact.
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.
supercent-io/skills-template
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
web-performance-optimization has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: web-performance-optimization is focused, and the summary matches what you get after install.
Keeps context tight: web-performance-optimization is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for web-performance-optimization matched our evaluation — installs cleanly and behaves as described in the markdown.
web-performance-optimization reduced setup friction for our internal harness; good balance of opinion and flexibility.
web-performance-optimization has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for web-performance-optimization matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: web-performance-optimization is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: web-performance-optimization is the kind of skill you can hand to a new teammate without a long onboarding doc.
web-performance-optimization has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 64