Content Image Adapter

One picture, two frames. The artwork does not change: no regeneration, no redraw, no restyle, no image service. What changes is the shape around it, and how the picture meets the edges of that shape.

The horizontal picture serves the feeds that show an image wide or at its own ratio, the vertical one serves the feeds that give a tall or square image more room and crop it toward the middle, and a platform whose frame differs from both crops its picture the way it crops any image. Two files cover every surface.

Nothing platform-specific lives here. Which picture each platform takes is the Picture column of the canonical table in awesome-content-campaign/references/platforms.md, with the research behind every row in that file's The picture each platform takes. This skill reads the column and adds nothing to it; with that file absent, which platforms need the vertical picture is asked of the user rather than guessed.

Bundled file (load on demand):

• references/geometry.md - the two pixel targets, how a picture is fitted into each, why one vertical serves square, 4:5 and full-height slots alike, and what the result has to satisfy before it ships. Read it before fitting the picture.

Two modes, and the mode is not asked

Alone. The user hands over an image and asks for post images. Two files are written into a new folder under the session's temporary area, horizontal.png and vertical.png. The folder is opened on the machine, and the absolute path is reported.

In a chain. awesome-content-repurpose has written the post files and the user has handed over a picture, or a still has been cut from their video. This skill runs without being asked again: the approved file goes in, and the two pictures land beside the post files: