SkillCheatSheet
How to install

alt-text

An AI skill for Claude Code, Cursor, Codex and other AI agents, from thedaviddias/Front-End-Checklist. Scored by fixed code checks, no AI.

CCode 58/100Builder 0/10

Use when reviewing image assets, markup, and CDN or build transforms related to Provide meaningful alt text for images. Check encoded size, rendered size, loading strategy, and above-the-fold impact together.
75k starsMITRepository score 64/10046 lines1 other file

Install

npx skills add thedaviddias/Front-End-Checklist --skill alt-text
Where do I paste this?

Open a terminal in your project folder, paste the command and press Enter. It needs Node.js on your computer.

Run it in your project. The skills CLI asks which agents to install it for (Claude Code, Cursor, Codex and more); add -g to install it for your user instead.

No terminal? Copy SKILL.md and give it to your AI as instructions.

SKILL.md

A skill is instructions and scripts your agent will follow, so read it before you install it. Its text loads here from GitHub; you can also read it on GitHub.

More skills from thedaviddias/Front-End-Checklist

Use 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.

Code 77/100

Use when auditing or improving any frontend codebase against the full Front-End Checklist rule corpus through one entry point.

Code 76/100

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.

Code 74/100

Use when reviewing image assets, markup, and CDN or build transforms related to Lazy load offscreen images. Check encoded size, rendered size, loading strategy, and above-the-fold impact together. Missing `loading='lazy'` is only a valid finding when you can reasonably tell the image is offscreen or

Code 69/100

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Avoid sensory-only instructions. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Code 65/100

Use 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.

Code 64/100

Use 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.

Code 64/100

Use 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 unk

Code 64/100
All skills in thedaviddias/Front-End-Checklist