Editorial Character Minimal Typography OG Image

Editorial Character Minimal Typography OG Image

Generate a polished 16:9 sharing image with a distinctive editorial character, precise headline typography, and a repeatable visual system.

Style: Editorial Character. Witty and composed, pairing a small expressive line-art character with confident editorial typography on a vivid, controlled ground. Follow references/style-guide.md exactly.

Use this skill when

• Product launches and feature announcements with one short headline
• Articles and publishing series that benefit from a recognizable illustrated voice

Do not use

• Photorealistic portraits, product mockups, or detailed scenes that need realistic material rendering
• Text-heavy announcements, data graphics, or layouts requiring several logos and calls to action
• To reproduce another company's brand, logo, product UI or copyrighted characters.

Inputs

• Fictional or user-provided product or publication name, if it should appear
• Exact headline text and optional short descriptor
• Audience, subject, or launch context to inform the character’s gesture
• Preferred accent color or permission to use the signature red ground

If something essential is missing, ask one short question before starting. Never invent facts, numbers, quotes or customer names; mark gaps as [needs source].

Workflow

1. Collect the brief fields listed in references/prompt-framework.md. If any text will appear in the image, confirm it letter by letter and freeze it.
2. Build the prompt with references/prompt-framework.md, following references/visual-system.md for subject, composition, light, palette and the text policy. Write it to prompt.txt.
3. Check that the generation key is configured: SKILLLOOM_API_KEY and SKILLLOOM_BASE_URL (run npx skillloom doctor --write-env if not).
4. Tell the user the image is paid from their prepaid key (see the cost note) and get explicit approval.
5. Generate one image. The task id is saved first, so re-running the same command resumes instead of paying twice:

``bash node scripts/generate.mjs --prompt-file prompt.txt --output image.png --task-file image-task.json --confirm-paid ``

1. Run the validator and fix every problem it reports:

``bash node scripts/validate-image.mjs image.png ``

What makes this excellent

• Treat the supplied headline as locked copy: preserve spelling, punctuation, capitalization, and line meaning exactly; do not add text.
• Choose one simple character action that makes the subject immediately understandable at thumbnail size, without relying on a real person or recognizable mascot.
• Build the layout on a quiet modular grid: headline occupies the broad left area and the character anchors the right, with safe margins for social crops.
• Keep the character drawing expressive but economical: consistent black line weight, a few solid fills, and no detailed setting or props beyond one relevant object.
• Use the fictional sample’s vivid red ground as the series signature; honor a user-requested color only when it maintains strong text contrast and visual consistency.
• Before delivery, inspect headline rendering at small preview size and regenerate if any characters are malformed, duplicated, or obscured.

Output contract

• One PNG at 16:9, at least 1200px wide, following the visual system; any approved text spelled exactly.
• No logos, watermarks or real people's likenesses unless the user owns them.
• A hand-off note with the final prompt, the task file path and the validator output.
• Deliver one 16:9 image at a minimum width of 1200 pixels, composed for Open Graph and social preview crops.
• Include only user-approved copy; do not invent a brand mark, URL, badge, or supporting claim.

Reference demo and agent run

The preview image was generated from the sample brief in scripts/image-spec.json. In a real run the agent fills the brief from the user's request, generates with the user's key, checks the result against the output contract (required text, ratio, no extra words) and regenerates when it misses.

Failure rules

• If the API reports a low balance or a limit, stop and tell the user; never switch providers or keys silently.
• If text is misspelled or the composition misses the visual system, ask before generating again. Never retry automatically; every attempt is paid.
• Never print or store the API key in files you hand over.