apple-image-representation-workflowlisted

Guide Apple image decoding, encoding, metadata, thumbnails, multi-frame sources, and representation bridging across Image I/O, Core Graphics, AppKit NSImage and NSImageRep, UIKit UIImage, Core Image, and Core Video. Use when image work involves files, data, representations, orientation, scale, color, metadata, or conversion rather than pixel effects or visual recognition.
gaelic-ghost/socket · ★ 6 · AI & Automation · score 69

Install: claude install-skill gaelic-ghost/socket

# Apple Image Representation Workflow ## Purpose Guide image source, destination, representation, and conversion work without flattening distinct Apple image types into a generic wrapper. Keep file encoding, rendered pixels, processing recipes, platform display containers, metadata, and auxiliary images visibly separate. ## When To Use - Use for Image I/O sources and destinations, metadata, thumbnails, incremental loading, multi-frame images, `CGImage`, `NSImage`, `NSImageRep`, `NSBitmapImageRep`, `UIImage`, and representation conversion. - Recommend `core-image-processing-workflow` when filters, compositing, RAW development, custom kernels, or rendering are primary. - Recommend the Vision workflow when the requested outcome is recognition or analysis rather than representation ownership. ## Single-Path Workflow 1. Classify the request: - source inspection or decoding - incremental loading or thumbnailing - metadata or auxiliary data - destination encoding or multi-frame output - Core Graphics raster ownership - AppKit representation or drawing - UIKit image display ownership - conversion or repair 2. Apply the Apple docs gate: - read current Image I/O, Core Graphics, AppKit, or UIKit documentation first - state the documented behavior relied on - check API, image-format, auxiliary-data, and platform availability before promising a decode, encode, or representation path - apply `../../shared/references/apple-image-type-ownership.md`