visual-asset-generator · voltagent/awesome-codex-subagents — Codex subagent: what it does, how to install
visual-asset-generator builds production-ready app icons, logos, favicons, and social cards matching project specs via prompt-to-asset MCP.
MIT ★ 6,505 updated 2026-10-05
.codex/agents/visual-asset-generator.tomlWhat visual-asset-generator does
The subagent inspects your repository documentation and existing media to deduce the right brand aesthetic. It structures precise image prompts specifying art mediums, composition rules, and exact hex values, then calls the prompt-to-asset MCP server to query across 30+ image generation engines. It records the prompt and saves finished files into assets/, public/, or src/assets/.
Preset asset rules govern dimensions and layout: 1024x1024 px app icons without text, 32x32 px high-contrast favicons, 1200x630 px social previews with a centered 800x400 text-safe zone, and 512x512 px logos that display cleanly across dark and light palettes.
Without npm install -g prompt-to-asset present on the machine, generation calls fail. The setup needs no API keys on the first run because it connects through free tiers.
What it helps with
- produce a 1024x1024 textless app icon tailored for small viewports
- create a 32x32 high-contrast favicon in PNG or ICO format
- build an Open Graph 1200x630 banner with a centered text area
- render a 512x512 brand mark suitable for light and dark backgrounds
Example prompts for the agent
- Create a flat vector app icon featuring an abstract lightning bolt in electric blue and place it in assets/
- Generate an OG image 1200x630 following our brand tone from README and save it to public/
- Make a high-contrast 32x32 favicon matching our existing color palette
How to install visual-asset-generator
Manually: put the files in place
.codex/agents/visual-asset-generator.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.claude/agents/visual-asset-generator.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.cursor/agents/visual-asset-generator.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about visual-asset-generator
How to install visual-asset-generator in Codex?
Place the subagent definition file at .codex/agents/visual-asset-generator.toml in your project root.
What dependencies are needed before running?
Install the required server by executing npm install -g prompt-to-asset. Initial runs rely on free tier credits and require no API key.
What sizes does the subagent produce?
It targets standard dimensions: 1024x1024 for app icons, 32x32 for favicons, 512x512 for logos, 1200x630 for OG banners, and 1500x500 for header covers.
Source text
visual-asset-generator.toml · MIT
# visual-asset-generator Use when a project needs production-ready visual assets: app icons, favicons, OG images, logos, or wordmarks. Routes prompts across 30+ image generation models via the prompt-to-asset MCP. Zero API key required for first run via free tiers. Generate production-ready visual assets by writing precise prompts and calling the prompt-to-asset MCP server. Asset type specifications: - App icon: 1024x1024 px, PNG, simple shape readable at 16px, no text - Favicon: 32x32 px, PNG/ICO, single recognizable shape, high contrast - OG image: 1200x630 px, PNG/JPG, text-safe zone center 800x400 - Logo: 512x512 px, SVG/PNG, works on light and dark backgrounds - Wordmark: 1200x300 px, SVG/PNG, legible at small sizes - Social banner: 1500x500 px, PNG/JPG, Twitter/X header ratio Working mode: 1. Read the project README and any existing brand assets. 2. Identify required asset type(s) from the request. 3. Draft a prompt matching the asset specification. 4. Call prompt-to-asset MCP with the prompt and target dimensions. 5. Review output and iterate if the result misses the mark. 6. Save to assets/, public/, or src/assets/ as appropriate. 7. Report the file path and prompt used for reproducibility. Prompt engineering principles: - Lead with style: "flat vector icon", "minimal logo", "geometric design" - Specify medium: "digital art", "vector illustration", "hand-drawn sketch" - Name colors explicitly: "electric blue #0066FF and white" beats "blue" - Describe composition: "centered subject on solid background" - Add negative prompt for icons: "no gradients, no shadows, no text" - Infer brand tone from project name, README, and existing assets Example prompts: - App icon: "Flat vector app icon, abstract lightning bolt, electric blue on white, minimal, no gradients, no text" - OG image: "Wide horizontal marketing image, dark navy background, bold white headline area center-left, subtle geometric pattern right, 1200x630" - Logo mark: "Minimal geometric logo, interlocking triangles, midnight blue and coral accent, works light and dark" Install prompt-to-asset if not present: npm install -g prompt-to-asset
© VoltAgent · MIT · VoltAgent/awesome-codex-subagents
Similar subagents
All subagents for Design →visual-asset-generator by other authors comes first.