Create production-ready prompts for brand and marketing images.
Workflow
- Classify request as one of:
site_logoui_iconfeatured_blog_imagesocial_og_imagefavicon_app_icon
- Collect required fields from the input matrix below. Ask only for missing required fields.
- Load the matching template from references/templates.md.
- Apply global quality rules:
- Keep one coherent visual language.
- Keep output clean and uncluttered.
- Avoid trademarked logo imitation or direct brand copying.
- Prefer legibility at small sizes for logo/icon outputs.
- Return results in this exact order:
Final prompt:Render settings:Variation ideas:
Input Matrix
| Type | Required | Optional |
|---|---|---|
site_logo |
brand_name, niche, style, primary_color, mood |
icon_concept, neutral_color, font_tone |
ui_icon |
icon_name, icon_purpose, icon_style, primary_color, size_context |
stroke_weight, corner_style |
featured_blog_image |
article_title, keywords, primary_color, image_style, tone |
visual_metaphor, focal_subject |
social_og_image |
brand_name, page_title, tagline, primary_color, bg_style |
domain_text, logo_position |
favicon_app_icon |
brand_symbol, shape, primary_color, secondary_color |
border_style, padding_ratio |
Defaults
Use defaults when optional fields are not provided:
neutral_color:slate grayfont_tone:clean modern sans-serifstroke_weight:1.5pxcorner_style:slightly roundedvisual_metaphor: derive from title + keywordsfocal_subject: abstract symbol tied to keyword intentdomain_text: include only if providedlogo_position:bottom-leftborder_style:nonepadding_ratio:12%
Multi-Asset Requests
If a user requests multiple assets in one turn:
- Generate one prompt block per asset type.
- Keep shared brand fields consistent (
brand_name, palette, mood). - Vary only what each artifact needs (size, composition, style constraints).
References
- Prompt templates: references/templates.md
- Registry examples: references/registry-snippets.ts