image-optimization-pipeline-config

What problem does it solve?

Prevent silent regressions in a build-time image optimization pipeline by making format, quality, transparency, and srcset breakpoints an explicit reviewable contract instead of implicit code behavior.

Core Features & Use Cases

• Config-as-contract image policy: Defines responsive srcset breakpoints, output formats (AVIF/WebP/JPEG fallback), and per-format compression quality so the pipeline behavior can be derived from configuration.
• Transparency-safe publishing: Ensures PNGs with transparency do not end up as lossy artifacts by routing them to alpha-preserving output paths.
• Idempotent build behavior: Requires the pipeline to skip already-optimized outputs via hash-based cache invalidation so repeated builds do not churn files.
• Use case: While reviewing changes to image tooling in a static site build, apply this skill to confirm the pipeline will preserve transparency, emit the expected variant set, and align emitted breakpoints with site layout breakpoints.

Quick Start

Use the image-optimization-pipeline-config skill to review whether your updates to lib/images/pipeline.config.ts, scripts/build-images.ts, or format negotiation rules preserve transparency, match expected srcset breakpoints, and maintain idempotent outputs.