best-practices

Audit web projects for security, compatibility, and code quality issues.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/Rayzerrek/dotfiles --skill best-practices-rayzerrek
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: best-practices
Source: https://github.com/Rayzerrek/dotfiles/tree/main/.pi/agent/skills/best-practices
Command: npx skills add https://github.com/Rayzerrek/dotfiles --skill best-practices-rayzerrek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you identify and apply modern web development best practices so you can ship secure, compatible, and high-quality frontend experiences with fewer regressions.

Core Features & Use Cases

  • Security hardening: Improve defenses with HTTPS, CSP, Trusted Types, SRI, safe cookies, and current security headers.
  • Compatibility review: Catch missing doctype, charset, viewport, deprecated APIs, and weak feature-detection patterns before release.
  • Code quality and UX checks: Spot invalid HTML, unsafe DOM usage, blocking scripts, event-handler inefficiencies, and poor permission or error-handling flows.
  • Use case: Review a production web app before launch to reduce Lighthouse best-practice issues, close common vulnerability gaps, and improve maintainability.

Quick Start

Review the attached web project and apply the best-practice checklist to surface security, compatibility, and code-quality fixes.

Frequently Asked Questions about best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my web app for security and code quality issues before launch?▼

To audit a web app for security and code quality, review the project against a best-practice checklist to surface HTTPS enforcement, CSP, SRI, valid HTML, and safe DOM handling fixes before release.

What security headers and policies do I need to harden my frontend application?▼

Frontend security hardening requires implementing HTTPS, Content Security Policy, Trusted Types, Subresource Integrity, safe cookies, and current security headers to close common vulnerability gaps.

How do I improve Lighthouse best-practice scores for a production web project?▼

Improving Lighthouse best-practice scores involves checking for valid HTML, performance-conscious loading, blocking scripts, and event-handler inefficiencies to reduce regressions and improve compatibility.

What common browser compatibility issues should I check before deploying a frontend?▼

Browser compatibility checks catch missing doctype, charset, viewport tags, deprecated APIs, and weak feature-detection patterns, ensuring smooth frontend modernization without breaking existing user environments.

Can I use this approach for a legacy frontend modernization review?▼

Yes, the review applies to frontend modernization by identifying deprecated APIs, unsafe DOM usage, and missing viewport or charset tags to update older web projects securely.