use case
Cover images for every post your agent writes.
Your agent drafts a blog post, then generates a matching cover image in the same flow. No separate design pass.
the problem
Why this is a pain.
Every blog post needs a cover. Every social share needs an image. You're not a designer, and stock photos look like stock photos. Hand-prompting an image-gen playground for every post breaks the writing flow and costs more time than the writing itself.
AI agents can draft the post, summarize the key idea, and describe a matching image — but they can't actually produce the image without an external tool you've glued in yourself. So the image step stays manual, and posts ship with no cover or with a hasty stock photo.
the workflow
How Frenchie handles it.
- 1
Ask your agent to draft the post and generate a matching cover in one prompt — `Write a 600-word post on async transcription pricing for dev tools, then generate an abstract technical cover image, warm amber and charcoal palette`. The same agent owns both halves of the deliverable.
- 2
Your agent drafts the post, extracts a visual concept from the content ("abstract technical illustration capturing the idea of asynchronous handoff"), and calls `generate_image` with a prompt it derives from the post body — concrete subject, palette, mood, composition.
- 3
Frenchie returns the image at `.frenchie/<post-slug>/cover.png` next to the post draft (20 credits = $0.20). For social variants — landscape OG, square Instagram, vertical story — your agent calls `generate_image` again with a different `size` parameter on the same prompt.
- 4
Your agent references the image in the post's frontmatter (`cover: ./cover.png`) or hands the path back to you for review. For weekly publishing cadence, the cost works out to about $10/year for 52 covers — less than a single month of stock-photo subscriptions.
example
What it looks like in practice.
Your prompt
Draft a 600-word post on pay-per-use vs subscription pricing for dev tools. Then generate a cover image — something abstract and technical, warm colors.
Agent response
Post drafted — .frenchie/pay-per-use-post/draft.md (612 words). Cover image generated — .frenchie/pay-per-use-post/cover.png (1024×1024, 20 credits). Prompt used: 'Abstract technical illustration, warm amber and charcoal palette, geometric tokens flowing across a grid, subtle halftone texture.'
What lands in your workspace
$frenchie generate "French bulldog eating pizza"
tips
Things worth knowing.
- 20 credits per cover. A post per week for a year is 52 × $0.20 = $10.40.
- Your agent can describe the image in words first — review the prompt before generating to avoid wasted credits.
- Pair with the ocr_to_markdown or transcribe_to_markdown tools in the same session if the post references a document or recording.
questions
Common questions.
Can I match my brand style?
Yes — include brand colors, typography cues, and composition in the prompt. Image generation responds to specific style direction better than vague aesthetic adjectives.
Can my agent generate social variants (landscape, square, vertical)?
Yes — pass aspect ratio as a parameter on generate_image. Your agent can loop through a set of sizes for one post.
Does this work for OpenGraph and blog platforms?
Yes — the image saves as a standard PNG file. Your agent can drop the path into your frontmatter, upload it to your CMS, or reference it inline in Markdown.
Try it with a real prompt of yours.
100 free credits on signup. No card. Give your agent a real image brief from your workflow and see what it creates.