SVG Hero Image Generator

Creates editable, information-dense SVG hero images for README files — the opposite of abstract art. Every element on the banner should trace back to a real, verifiable fact about the repository: its name, its stack, its purpose, its badges. Nothing decorative for decoration's sake, nothing invented.

This is a communication design task, not a generative-art task: the goal is instant legibility of who this project is, not an emergent aesthetic experience. If the repo is sparse or unknown, say so and default to the safest minimal direction rather than inventing facts to fill space.

Workflow

This happens in three passes. Do not skip ahead to rendering — the whole value of this skill is that the banner is earned by inspecting the repo first, not guessed at.

Pass 1 — Inspect the repository

Before proposing anything, gather real signals using your actual tools (view, bash_tool), not by guessing:

• Read README.md if present — title, tagline, badges, tone of the prose.
• Check for manifest/build files that reveal the stack: package.json, pyproject.toml, requirements.txt, go.mod, Cargo.toml, pom.xml, build.gradle*, Dockerfile, docker-compose.*, .github/workflows/*.
• Look for existing brand signals: a logo, favicon, existing /assets, /docs, /public, /static images, or a color already used somewhere (badge colors, existing SVGs).
• Note the project's apparent tone — experimental hobby project, hacker CLI, polished commercial library, academic tool, enterprise platform — since this drives typography and density, not just color.