CtrlK
BlogDocsLog inGet started
Tessl Logo

responsive-images

Use when reviewing article images, cards, galleries, or any component rendered at multiple sizes across breakpoints. Check both the markup and the CSS layout because an incorrect `sizes` attribute can negate a perfectly good `srcset`.

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/responsive-images/SKILL.md
SKILL.md
Quality
Evals
Security

Implement responsive images with srcset

Serving a 2000px image to a 400px phone screen wastes bandwidth and slows loading—srcset lets the browser download only the size it needs.

Quick Reference

  • Use srcset to provide multiple image sizes
  • Use sizes attribute to tell browser which size to download
  • Browser selects optimal size based on viewport and DPR
  • Can save 50-70% bandwidth on mobile devices

Check

Verify that images use srcset and sizes attributes for responsive delivery.

Fix

Implement responsive images with srcset for different screen sizes and resolutions.

Explain

Explain how responsive images deliver optimized versions based on device capabilities.

Code Review

Inspect image markup and component abstractions for srcset, sizes, and width/height handling. Flag pages that always ship desktop-sized assets to mobile, omit sizes, or generate variants that do not match the actual rendered layout.


For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/en/rules/images/responsive-images

Repository
thedaviddias/Front-End-Checklist
Last updated
First committed

Is this your skill?

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.