domains / families / design / image-processing

image-processing

combined

Batch-convert and compress local images with Pillow; use when you need an offline, scriptable pipeline for directory-based processing. Process images for web development — resize, crop, trim whitespace, convert formats (PNG/WebP/JPG), optimise file size, generate thumbnails, create OG card images. Uses Pillow (Python) — no ImageMagick needed. Trigger with 'resize image', 'convert to webp', 'trim logo', 'optimise images', 'make thumbnail', 'create OG image', 'crop whitespace', 'process image', or 'image too large'.

When to use

• You need to batch convert a folder of images into a single target format (e.g., WebP) for distribution.
• You want to reduce file sizes via compression while keeping processing fully offline (no network calls).
• You need a repeatable, scriptable pipeline for CI/local automation (e.g., preparing assets for a website/app).
• You want to preserve the source directory structure in the output directory during conversion.
• You need best-effort batch processing where individual file errors are reported but do not stop the entire run.

When not to use

• Do not use this skill when the required source data, identifiers, files, or credentials are missing.
• Do not use this skill when the user asks for fabricated results, unsupported claims, or out-of-scope conclusions.
• Do not use this skill when a simpler direct answer is more appropriate than the documented workflow.

Skill page

Conflict

The two skills cover overlapping ground (Pillow-based image processing) but serve different primary workflows. The first skill (jezweb) focuses on a CLI tool (`img-process`) for individual operations like resizing, trimming, and generating OG cards, providing specific Python patterns for these tasks. The second skill (aipoch) focuses on a batch directory conversion script (`convert_images.py`) with specific flags for recursion, overwriting, and error handling, emphasizing a CI/automation pipeline. Neither is a strict reproduction of the other; the first lacks the batch directory logic and error-handling contract of the second, while the second lacks the specific utility commands (trim, OG card) and code patterns of the first. Combining them provides a complete toolkit for both single-file manipulation and batch directory processing.