marketing-image-generation

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
name: marketing-image-generation
description: Generate high-quality marketing images, ad creatives, launch visuals, social cards, blog headers, product mockups, thumbnails, and campaign assets. Use when the user asks to create, design, iterate on, or prompt an image for marketing, growth, social media, paid ads, landing pages, newsletters, or product launches.
---

# Marketing Image Generation

## Core Workflow

1. Identify the asset type: ad, social post, blog header, hero image, launch graphic, thumbnail, email banner, product mockup, or campaign visual.
2. Gather only missing essentials: goal, audience, channel, dimensions or aspect ratio, required copy, brand constraints, product context, and output count.
3. Check available context before asking: README, `DESIGN.md`, brand files, existing screenshots, product copy, and any user-provided reference images.
4. Draft a concrete visual direction before generating: subject, layout, composition, style, color palette, typography direction, lighting, mood, camera/framing, and constraints.
5. Use the image generation tool only when the user has explicitly asked for an image asset or visual mockup.
6. Review the result against the brief, then iterate with targeted changes instead of rewriting the whole concept.

## Marketing Defaults

- Prefer one strong focal point over collages.
- Make the product, benefit, or audience instantly legible at thumbnail size.
- Use short text in images. If copy is required, preserve it exactly and keep it to a headline or label.
- For product-led assets, show a plausible interface, workflow, or user outcome rather than decorative UI fragments.
- For paid ads, optimize for immediate comprehension, contrast, and a clear emotional hook.
- For editorial/blog assets, prefer a concept-driven image that supports the article thesis without repeating the title literally.

## Patterns to Avoid (AI Slop)

These are the tells of machine-generated marketing design. They cluster because
they're what an image/layout model reaches for by default — which is exactly why
they read as generic. The goal isn't to memorize a blocklist; it's to recognize
the family so you avoid the next variant too. The underlying principle: every
element should earn its place by carrying meaning or hierarchy. If it's there only
to look "designed," cut it.

Avoid these unless the user explicitly asks for one:

- **Eyebrow pills above the headline.** The little rounded badge with label text
  ("✨ INTRODUCING", "NEW", "v2.0") floating above the H1. It almost never adds
  information the headline doesn't already carry, and it's the single most common
  AI-layout tell. Lead with the headline itself.
- **Gradient-filled or glowing buttons.** Multi-color gradient fills, neon glow,
  or animated-looking sheen on CTAs. Use a single solid accent color with a
  flat or very subtle shadow. A button should look pressable, not radioactive.
- **The default purple→pink/violet tech gradient.** Indigo-to-magenta backgrounds
  (the generic "AI startup" wash) signal template, not brand. Anchor color in the
  product's actual palette. A gradient is fine when it's restrained and on-brand —
  the problem is reaching for *that* gradient as a default.
- **Emoji and sparkle (✨/🚀/⚡) ornament.** Decorative emoji used as design
  elements rather than content. They cheapen the composition and date instantly.
- **Glassmorphism everywhere.** Frosted, semi-transparent blurred cards stacked in
  depth for no functional reason. One blurred foreground card can work (see
  `examples/blurred-bg-foreground-component.html`); a whole scene of them is slop.
- **Generic startup imagery.** Floating dashboards without context, handshake
  photos, rocket/lightbulb metaphors, vague abstract 3D — blobs, glossy spheres,
  isometric doodads, gradient orbs that don't represent anything.
- **Decoration over hierarchy.** Heavy drop shadows on every element, oversized
  border-radius on everything, neon glow text, and centered-everything