Explore skills
Showing 71671–71700 of 75619 skills
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Fix empty and broken links. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing scripts, client components, bundles, or runtime behavior related to Implement proper error handling. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing image assets, markup, and CDN or build transforms related to Handle image loading errors gracefully. Check encoded size, rendered size, loading strategy, and above-the-fold impact together.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when setting up a new project's production observability stack, reviewing incident response readiness, or investigating why errors are going undetected.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing scripts, client components, bundles, or runtime behavior related to Use ES modules (import/export). Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing scripts, client components, bundles, or runtime behavior related to Use event delegation for dynamic content. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when auditing content pages for citation quality, suggesting authoritative sources to link for factual claims, or reviewing whether a page's external link attributes (nofollow, noopener) are correctly set.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when adding FAQ sections to landing pages or blog posts, generating FAQPage JSON-LD from existing Q&A content, or validating that structured data on pages with FAQ sections is syntactically and semantically correct.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when checking whether a site has a correctly configured favicon, auditing `<link rel='icon'>` tags in the `<head>`, or setting up favicon infrastructure for a new project.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing templates, rendered HTML, or shared components related to Implement favicons for all devices. Validate the final browser-facing markup, not just the source framework abstraction.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when optimising Largest Contentful Paint (LCP), reducing render-blocking resource contention, or fine-tuning resource loading order in the critical rendering path.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing image assets, markup, and CDN or build transforms related to Use <figure> and <figcaption> for image captions. Check encoded size, rendered size, loading strategy, and above-the-fold impact together.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing templates, rendered HTML, or shared components related to Make file uploads accessible. Validate the final browser-facing markup, not just the source framework abstraction.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing image assets, markup, and CDN or build transforms related to Use descriptive image filenames. Check encoded size, rendered size, loading strategy, and above-the-fold impact together.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when you need to find the 2-3 most popular and well-maintained npm packages relevant to a frontend checklist rule, validate they meet quality thresholds, and add them to the rule's frontmatter.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when auditing slow page loads, heavy assets, or rendering delays related to Optimize first contentful paint. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing rendered HTML, interactive components, or design-system patterns related to Prevent seizure-triggering flashing content. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing stylesheets, component styles, and responsive behavior related to Apply Flexbox best practices. Check the rendered layout across breakpoints and interaction states before proposing a fix.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing rendered HTML, interactive components, or design-system patterns related to Manage focus during dynamic interactions. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing sticky navigation, consent banners, chat widgets, skip links, or any fixed-position UI. Validate the actual tab order and viewport behavior at realistic zoom levels.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure logical focus order. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing stylesheets, component styles, and responsive behavior related to Provide visible custom focus indicators. Check the rendered layout across breakpoints and interaction states before proposing a fix.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when auditing slow page loads, heavy assets, or rendering delays related to Optimize web font loading. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when applies to all CSS `font-size` declarations, particularly those using `px` units for body text, UI labels, and navigation. Use when auditing mobile responsiveness and accessibility compliance. Check for `font-size` in media queries targeting small screens.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing public HTML forms (no authentication required to reach them) for bot and abuse protection mechanisms.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing rendered HTML, interactive components, or design-system patterns related to Use a single label for each form field. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing HTML forms, fetch/XHR calls, and form action attributes to ensure data is submitted exclusively over HTTPS.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing rendered HTML, interactive components, or design-system patterns related to Associate labels with form controls. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing templates, rendered HTML, or shared components related to Validate forms accessibly. Validate the final browser-facing markup, not just the source framework abstraction. Distinguish between browser-posted forms and client-handled React forms so you do not over-report missing `method` or `action` as accessibility defects.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing rendered HTML, interactive components, or design-system patterns related to Provide titles for iframes and frames. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodex