image-work

Enforce consistent image rendering with alt text, placeholders, and widths.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/Wahidul123/med-plus-hub --skill image-work-wahidul123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: image-work
Source: https://github.com/Wahidul123/med-plus-hub/tree/main/.emdash/skills/image-work
Command: npx skills add https://github.com/Wahidul123/med-plus-hub --skill image-work-wahidul123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Image handling and media galleries are a common source of inconsistency in UI. This skill provides guidance to consistently render images, manage placeholders, and build media galleries across components.

Core Features & Use Cases

  • Enforce the use of a single Image component from the UI library for consistency.
  • Provide clear patterns for user-provided URLs, CMS/API URLs, and placeholder images with unique IDs.
  • Include accessibility and performance best practices, such as alt text discipline, lazy loading, and explicit widths.

Quick Start

Apply the Image component to render images with proper alt text, placeholders, and width specifications.

Frequently Asked Questions about image-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What's the best way to standardize React image components for UI consistency?

Standardize React image rendering by enforcing a single Image component for all media. This enforces descriptive alt text, placeholder URL guidelines, and explicit width recommendations to maintain visual and accessibility consistency across UI galleries.

How do I manage placeholder images and user-provided URLs in a React gallery?

Manage placeholder images and user-provided URLs by applying consistent patterns for CMS/API integration. Use unique IDs for placeholders and enforce explicit width specifications to ensure reliable rendering across media galleries.

Does TypeScript help enforce accessibility requirements like alt text for images?

TypeScript helps enforce accessibility by requiring descriptive alt text for image components. This approach ensures accessibility best practices are applied consistently, preventing missing or empty alt attributes in UI-heavy applications.

Why should I use a single image component instead of native img tags for hero sections?

Use a single image component instead of native img tags to enforce lazy loading, explicit widths, and alt text discipline. This guarantees performance and accessibility best practices are met across hero sections and avatars.

Can I use this approach for both user-provided and CMS API image URLs?

Yes, this approach handles both user-provided and CMS API image URLs. It provides clear rendering patterns for each source, ensuring consistent display quality and accessibility compliance regardless of the image origin.