landing page image quality
via PatrickJS/awesome-cursorrules
Use real, optimized images with proper alt text and responsive constraints instead of placeholders.
What is landing page image quality?
This rule guides you to replace placeholder image services with real, licensed assets and ensure proper accessibility, dimensions, and responsive behavior. Use it whenever generating or editing user-facing pages to maintain visual quality and prevent layout shifts.
- Replace placeholder services (placehold.co, via.placeholder.com, dummyimage.com, picsum.photos) with committed project assets or approved stable URLs
- Verify image licenses and attribution requirements are compatible with the project before use
- Provide explicit width, height attributes or CSS aspect-ratio constraints to prevent layout shift
- Write specific alt text for informative images and empty alt for decorative images
- Ensure image paths resolve in the built application and check responsive behavior at mobile and desktop widths
- Use consistent aspect ratios for repeated cards or gallery items and match images to actual content they represent
Applies to
File patterns this rule matches.
Rule definition (reference)
Source of truth, from the repository.
Landing Page Image Quality
When generating or editing user-facing pages, use real, relevant visual assets instead of placeholder image services.
Image Sources
- Do not commit
placehold.co,via.placeholder.com,dummyimage.com,picsum.photos, random image URLs, or broken/deprecated image services. - Prefer committed project assets, product screenshots, generated assets approved by the user, or stable URLs from an approved image provider.
- Before using a third-party image, confirm the license and attribution requirements are compatible with the project.
- Avoid hotlinking images from arbitrary websites.
Asset Quality
- Match images to the actual content, product, place, object, or user state they represent.
- Do not use vague atmospheric images when the user needs to inspect a product, feature, workflow, or interface.
- Use consistent aspect ratios for repeated cards or gallery items.
- Provide explicit
widthandheightattributes or CSS aspect-ratio constraints to prevent layout shift. - Use optimized formats and sizes appropriate for the target framework.
Accessibility
- Every informative image must have specific
alttext that describes the image's purpose in context. - Decorative images must use empty alt text and should not be announced to assistive technology.
- Do not put essential text only inside an image.
Implementation Checks
- Ensure image paths resolve in the built application.
- Check responsive behavior at mobile and desktop widths.
- Verify that loading, error, and empty states do not leave broken image icons in production UI.
Related rules
Laravel package development guide with PHP 8.3 features and best practices
Expert guidance for Laravel development with TALL Stack (Livewire, Alpine.js, Tailwind CSS) best practices.
Pipeline for downloading, quantizing, and uploading models with NVIDIA CUDA and AMD ROCm support on Linux.
YAML-based backend scaffolding for Manifest app development with structured entity and property definitions.

Expert guidance for building applications with Medusa, TypeScript, React, and TailwindCSS.
Expert guidance for building with Medusa, TypeScript, React, and TailwindCSS.