Explore skills
Showing 71731–71760 of 74427 skills
Use when reviewing or improving a Front-End Checklist rule MDX file to raise its quality score, fix stub prompts, add missing fields, or enrich content with real code examples.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing rendered HTML, interactive components, or design-system patterns related to Use inclusive language. 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 auditing a site for accidental noindex directives, investigating why important pages are not appearing in Google Search, or reviewing CMS settings that control indexing at the page or category level.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when auditing a site for indexability issues, investigating why pages appear in Google's index that should be excluded (or vice versa), or reviewing robots.txt and meta robots configurations for consistency.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing rendered HTML, interactive components, or design-system patterns related to Provide alt text for image buttons. 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 Use semantic input type attributes. Validate the final browser-facing markup, not just the source framework abstraction.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing CI coverage, automated checks, or test strategy related to Write integration tests for key workflows. Focus on whether the rule is continuously verified, not just documented.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when auditing slow page loads, heavy assets, or rendering delays related to Optimize interaction to next paint. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when auditing a site's internal link structure, identifying pages that need more incoming links, generating contextual linking opportunities between related content, or reviewing a CMS template's internal linking patterns.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when applies to CSS and JavaScript implementations of modals, overlays, pop-ups, cookie banners, newsletter sign-up dialogs, and promotional overlays. Check for `position: fixed`, `position: absolute` with large z-index, backdrop overlays, and JavaScript that shows modals on page load or shortly after. Consider both SEO impact (Google) and accessibility (WCAG focus management).
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when auditing a page's link elements for crawlability, reviewing JavaScript-heavy SPAs where navigation may not use `<a href>` tags, or checking that dynamically generated links have valid href values.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing scripts, client components, bundles, or runtime behavior related to Avoid inline JavaScript. 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 Lint JavaScript code. 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 Minify all JavaScript files. 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 slow page loads, heavy assets, or rendering delays related to Optimize JavaScript bundle size. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when auditing slow page loads, heavy assets, or rendering delays related to Use secure and up-to-date JS libraries. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when auditing slow page loads, heavy assets, or rendering delays related to Avoid JavaScript-based redirects. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when generating or auditing any `<script type='application/ld+json'>` blocks, implementing structured data for articles, products, FAQs, breadcrumbs, or local businesses, or investigating why rich results are not appearing in Google Search Console.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing scripts, client components, bundles, or runtime behavior related to Parse JSON safely with 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 rendered HTML, interactive components, or design-system patterns related to Enable keyboard navigation for all elements. 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 auditing content pages for over-optimisation, reviewing AI-generated content that may repeat target phrases excessively, or checking meta tags and alt text for unnatural keyword accumulation.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing rendered HTML, interactive components, or design-system patterns related to Align visible labels with accessible names. 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 rendered HTML, interactive components, or design-system patterns related to Use exactly one main landmark. 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 rendered HTML, interactive components, or design-system patterns related to Use landmark regions correctly. 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 applies to all HTML documents. Check the `<html>` opening tag for a `lang` attribute with a non-empty, valid BCP 47 language code. Also check for `lang` attribute changes on individual elements when the document contains content in multiple languages (inline quotes, foreign terms, multilingual sections). The `lang` attribute is inherited — child elements inherit the language from their nearest ancestor with `lang`.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when auditing slow page loads, heavy assets, or rendering delays related to Optimize largest contentful paint. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when auditing slow page loads, heavy assets, or rendering delays related to Disable lazy loading for above-the-fold content. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when auditing slow page loads, heavy assets, or rendering delays related to Implement lazy loading for offscreen content. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes. Absence of `loading='lazy'` is not enough by itself when fold position is unknown.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when reviewing client-side JavaScript, HTML source, or git history for exposed credentials, API keys, or tokens.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodexUse when auditing slow page loads, heavy assets, or rendering delays related to Avoid serving legacy JavaScript to modern browsers. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
thedaviddias/Front-End-Checklist
Stars: 74kClaude CodeCodex