Use when reviewing image assets, markup, and CDN or build transforms related to Use <picture> with an <img> fallback. Check encoded size, rendered size, loading strategy, and above-the-fold impact together.
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/picture-element/SKILL.mdA <picture> without an <img> fallback renders nothing in browsers that don't support <picture> (IE11) or don't support any of the <source> formats. The <img> child is also where alt, width, height, loading, and fetchpriority attributes live—these apply regardless of which source the browser selects.
<picture> must end with an <img> element—it is the required fallback and carries alt<source> elements are evaluated top-to-bottom; the first match winstype="image/avif" and type="image/webp" on <source> for format selection<img src> should point to a JPEG or PNG—the universal fallback for all browsersScan all
For each
Explain how the
Review image assets, markup, and delivery configuration related to Use
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/images/picture-element
thedaviddias/Front-End-Checklist
e8d14d0
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.