IconFlow turns product intent into an editable SVG, then makes the design survive native pixels, platform crops, and a source-bound review before any asset ships.
The agent researches the product, explores distinct concepts, and authors semantic SVG. IconFlow provides the playbook, deterministic renderer, quality gate, target transforms, and learning loop. It is not a prompt-to-image generator.
Choose your path
Two doors. One quality gate.
Use the agent path when you want help with product thinking and SVG craft. Use the CLI path when you already own the design decisions. Both end at the same review contract.
RecommendedAgent-assisted
Describe the product job, not the picture.
Install the open-format IconFlow skill. A compatible agent can discover the workflow when you ask for an app icon, favicon, logo mark, or tray icon.
Using another AI agent? Any agent that can read repository instructions and run shell commands can use IconFlow through AGENTS.md plus the CLI. Automatic skill discovery depends on the client.
Five-minute engine proof
Prove the pipeline before designing.
This builds IconFlow’s packaged reviewed family into a disposable work directory. It proves your environment—not that a distinctive new identity can be designed in five minutes.
01InstallGet the current PyPI release.
02Set upInstall Chromium once.
03Run proofRevalidate the receipt and build 23 assets.
demo verifies the packaged source and review contract, reruns QA, and writes web, PWA, Tauri desktop, Electron, and tray assets under iconflow-demo/build/.
source hash matches
0 automated warnings
six scores ≥ 4/5
Start with intent
Give the agent a useful brief.
A noun-only prompt produces decoration. Include the product’s job, audience, personality, palette, clichés to avoid, and exact output surfaces.
BRIEF / 01What the agent needs
Product intent
What does the product enable?
User job
What progress is the user making?
Essence
One word that guides every choice.
Personality
Two or three traits with tension.
Clichés
The obvious category symbols to reject.
Targets
Web, PWA, desktop, tray—or only what exists.
Agent prompt
Use the IconFlow skill to design, review, and ship a distinctive icon family for this project.
Product intent: [what the product enables]
User job: [the progress a person wants]
Essence: [one word]
Personality: [two or three traits]
Existing palette: [tokens or colors]
Clichés to avoid: [obvious symbols]
Targets: [web, pwa, tauri, electron, tray]
Keep the editable SVG and iconflow.toml in this project. Show me the concept bake-off and native-size review before shipping. Do not stop before recording the case.
Universal fallback
No skill discovery? Give the agent the contract.
This works with an agent that can read files and execute the local Python CLI, even when its client does not support Agent Skills.
Read [ICONFLOW_REPO]/AGENTS.md completely.
Use [ICONFLOW_REPO]/.venv/.../python -m iconflow ...
Keep your shell in this consuming project.
Follow concept → compare → check → review → ship → case.
The complete loop
Every command earns its place.
Run these from the consuming project. Use the IconFlow virtual-environment Python by absolute path so your config and final sources stay with the product they belong to.
01
Brief
Write the product contract.
Record intent before drawing. The config also fixes targets, colors, paths, and tray behavior.
Install from PyPI.Run pip install iconflow, or uv tool install iconflow. A source checkout stays available for contributors.
One-time download.Setup needs network access for dependencies and Playwright Chromium; rendering and builds are local afterward.
Desktop scope.Tauri output currently covers desktop assets, not Android or iOS launch and icon sets.
Toolchain-bound proof.Repeatability assumes the same normalized SVG, config, IconFlow, Chromium, and Pillow versions.
Ready for your project
Start with the job. End with evidence.
Run the engine proof once. Then open your product repository, give the agent a concrete brief, and keep every design decision where future maintainers can inspect it.