agentleFS
gronizgroniz/groniz-cli/skills/blog-cover-image/SKILL.md

blog-cover-image

Skill2 starsChanged 3 months agoApache-2.0View on GitHub

Generate and revise raster cover images for blog posts and articles from a title, brief, draft, local file, URL content supplied by the user, or reference images. Use when Codex needs to create a blog cover, article hero/header image, editorial thumbnail, Open Graph/social preview visual, or a channel-specific cover variant, including selecting composition, palette, rendering, text density, mood, font style, and aspect ratio.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. alfredang/ai-cms★ 4same name
    2. alfredang/ai-pei★ 1same name
    3. alfredang/ai4kids★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

31 rules. 0 are common, 29 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 29

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a clear, content-led raster cover that works at its intended display size.

    line 8
  2. Distinctive:

    Read the supplied content before designing.

    line 12
  3. Distinctive:

    Use an available raster image-generation or image-editing capability.

    line 15
  4. Distinctive:

    Do not substitute SVG, HTML, CSS, canvas, or another code-rendered visual unless the user explicitly requests that output.

    line 16
  5. Distinctive:

    If no raster backend is available, report the limitation and ask the user how to proceed.

    line 17
  6. Distinctive:

    Do not alter the source article while creating its cover.

    line 18
  7. Distinctive:

    Do not patch misspelled or garbled generated text by painting over the bitmap.

    line 19
  8. Distinctive:

    Prefer explicit user choices.

    line 32
  9. Distinctive:

    Use these defaults when no better signal exists:

    line 34
  10. Distinctive:

    Use requested pixel dimensions when provided.

    line 48
  11. Distinctive:

    Use six independent dimensions.

    line 52
  12. Distinctive:

    Read auto-selection.md when one or more dimensions are unspecified.

    line 63
  13. Distinctive:

    Treat compatibility tables as recommendations, not prohibitions.

    line 72
  14. Distinctive:

    Prefer a meaningful focal idea over a collage of literal keywords.

    line 88
  15. Very specific:

    If reference images are supplied, inspect them before composing the prompt.

    line 92
  16. Distinctive:

    Use the exact supplied title.

    line 102
  17. Very specific:

    Prefer none when the title is long, the destination already renders the headline, or the backend is unreliable with the required script.

    line 103
  18. Distinctive:

    Keep a title short enough to remain legible at thumbnail size.

    line 104
  19. Distinctive:

    Do not invent a subtitle merely to fill space.

    line 105
  20. Distinctive:

    Read base-prompt.md and prompt-template.md.

    line 109
  21. Distinctive:

    When working in a filesystem and an output directory is in scope, save the final prompt before generation:

    line 120
  22. Distinctive:

    Use a two-to-four-word lowercase kebab-case slug.

    line 130
  23. Distinctive:

    Use the backend explicitly requested by the user.

    line 136
  24. Distinctive:

    Prefer the current runtime's native raster image capability.

    line 137
  25. Distinctive:

    Use the only available compatible raster backend.

    line 138
  26. Distinctive:

    If multiple materially different backends remain, ask the user to choose.

    line 139
  27. Distinctive:

    No unintended words, watermarks, logos, UI fragments, extra limbs, or irrelevant objects

    line 151
  28. Distinctive:

    If a required check fails, preserve the flawed candidate, strengthen the prompt, and regenerate once.

    line 155
  29. Distinctive:

    Create a new prompt record before each regeneration.

    line 170
  30. Distinctive:

    Keep the core visual identity stable across channel variants.

    line 171
  31. Distinctive:

    Use image editing for localized visual changes when the active backend supports it.

    line 172

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Blog Cover Image

Create a clear, content-led raster cover that works at its intended display size.

Guardrails

  • Read the supplied content before designing. Treat its title, subject, tone, and claims as authoritative.
  • Preserve the exact user-provided or source title. Never invent a title, subtitle, logo, endorsement, product UI, statistic, or brand element.
  • Honor explicit brand guidelines, reference images, dimensions, file format, safe areas, and output paths before applying this skill's defaults.
  • Use an available raster image-generation or image-editing capability. Read and follow that capability's own instructions before invoking it.
  • Do not substitute SVG, HTML, CSS, canvas, or another code-rendered visual unless the user explicitly requests that output.
  • If no raster backend is available, report the limitation and ask the user how to proceed.
  • Do not alter the source article while creating its cover.
  • Do not patch misspelled or garbled generated text by painting over the bitmap. Regenerate with a stronger prompt or remove in-image text.

Resolve Inputs

Collect or infer:

  • Content source: title, topic, brief, draft, or article path
  • Intended placement or channel
  • Output location and format
  • Aspect ratio or pixel dimensions
  • Text to render, if any
  • Brand constraints and reference images

Prefer explicit user choices. Infer omitted choices when the content and destination make the answer clear; ask only when an unresolved choice would materially change the result.

Use these defaults when no better signal exists:

SettingDefault
Aspect ratio16:9
TypeAuto-select from content
PaletteAuto-select from content
RenderingAuto-select from content
Texttitle-only for a short supplied title; otherwise none
Moodbalanced
Fontclean
LanguageMatch the source or user request
FormatPNG

Use requested pixel dimensions when provided. Otherwise treat aspect ratio as the contract and let the active raster backend choose supported dimensions.

Design Dimensions

Use six independent dimensions. A style preset is only shorthand for palette and rendering; explicit settings override it.

DimensionValues
Typehero, conceptual, typography, metaphor, scene, minimal
Palettewarm, elegant, cool, dark, earth, vivid, pastel, mono, retro, duotone, macaron
Renderingflat-vector, hand-drawn, painterly, digital, pixel, chalk, screen-print
Textnone, title-only, title-subtitle, text-rich
Moodsubtle, balanced, bold
Fontclean, handwritten, serif, display

Read auto-selection.md when one or more dimensions are unspecified. Read only the selected dimension references needed to build the final prompt:

  • types.md for composition type
  • palettes/ for the selected palette
  • renderings/ for the selected rendering
  • text.md, mood.md, and font.md for the remaining dimensions
  • compatibility.md when combining unusual choices
  • style-presets.md when the user names a preset

Treat compatibility tables as recommendations, not prohibitions.

Workflow

1. Analyze the Content

Identify:

  • Exact title and optional subtitle
  • Central idea in one sentence
  • Audience and intended outcome
  • Tone and emotional intensity
  • Three to eight concrete keywords
  • One strong visual metaphor or focal subject
  • Visuals to avoid because they would be misleading, generic, or off-brand

Prefer a meaningful focal idea over a collage of literal keywords.

2. Inspect References

If reference images are supplied, inspect them before composing the prompt. Read reference-images.md and classify each reference as direct, style, palette, or composition guidance.

Describe observable traits such as layout, colors, line quality, texture, lighting, subject placement, and typography. Do not rely on vague instructions such as "make it similar."

3. Select a Cover Specification

Choose the six dimensions, aspect ratio, language, text content, and output format. Use option-selection.md when choices are missing or conflicting.

For in-image text:

  • Use the exact supplied title.
  • Prefer none when the title is long, the destination already renders the headline, or the backend is unreliable with the required script.
  • Keep a title short enough to remain legible at thumbnail size.
  • Do not invent a subtitle merely to fill space.

4. Build a Reproducible Prompt

Read base-prompt.md and prompt-template.md. Write one self-contained prompt containing:

  • Content context
  • Exact text, or an explicit instruction to render no text
  • Aspect ratio and intended placement
  • Type and spatial composition
  • Palette with concrete colors
  • Rendering, mood, and typography treatment
  • Required reference-image traits
  • Negative constraints

When working in a filesystem and an output directory is in scope, save the final prompt before generation:

<output-dir>/
├── prompts/
│   └── 01-cover-<slug>.md
├── refs/                         # only when references are persisted
└── cover.<ext>

Use a two-to-four-word lowercase kebab-case slug. Preserve existing candidates by incrementing the prompt and output filenames for revisions.

5. Generate the Raster Image

Select the backend in this order:

  1. Use the backend explicitly requested by the user.
  2. Prefer the current runtime's native raster image capability.
  3. Use the only available compatible raster backend.
  4. If multiple materially different backends remain, ask the user to choose.

Pass the final prompt, requested aspect ratio or dimensions, and every direct reference through the backend's supported interface. If the backend manages output paths, report that path; if it supports a target path, write to the agreed location.

6. Inspect and Validate

Inspect the generated image whenever the runtime permits it. Verify:

  • Correct aspect ratio and usable crop
  • One clear focal point and readable hierarchy
  • Accurate, legible, exact text
  • Adequate contrast and safe margins
  • No unintended words, watermarks, logos, UI fragments, extra limbs, or irrelevant objects
  • Required reference and brand traits are visible
  • The image still communicates at thumbnail size

If a required check fails, preserve the flawed candidate, strengthen the prompt, and regenerate once. Ask for direction after repeated subjective failures; continue iterating automatically on objective failures such as wrong text or dimensions when the backend permits.

7. Report Completion

Return:

  • Final image or its path
  • Type, palette, rendering, text, mood, font, and aspect ratio
  • Prompt path when saved
  • Reference count
  • Any limitation that remains, especially imperfect generated text

Revisions and Variants

  • Preserve the original cover unless the user explicitly asks to overwrite it.
  • Create a new prompt record before each regeneration.
  • Keep the core visual identity stable across channel variants; adjust crop, safe area, text density, and composition for each aspect ratio.
  • Use image editing for localized visual changes when the active backend supports it; regenerate when the requested change affects composition or text.
  • Limit post-processing to crop, resize, compression, and format conversion unless the user explicitly requests a composite workflow.

Reference Index

  • Selection: auto-selection.md, compatibility.md, style-presets.md
  • Composition: types.md, visual-elements.md
  • Prompting: base-prompt.md, prompt-template.md
  • References: reference-images.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.