Everyone who has ever built a landing page has lived this exact frustration. You need six little icons for your feature grid. You find a perfect search icon in one pack. A passable settings icon in a second pack. A 'security' shield in a third. And by the time you have all six, they look like they were drawn by six different people across six different decades — different stroke weights, different corner radii, one of them inexplicably has a gradient. Matching icons across packs is genuinely, surprisingly hard, and it's the kind of fiddly work that eats an hour and produces something that's STILL slightly off.
What I actually needed
I was building a SaaS feature-comparison section and needed icons for six concepts: Dashboard, Analytics, Integrations, Team, Security, and Support. Outline style, my brand's slate blue, on white. In the old workflow that's forty minutes of browsing and a nagging feeling that the analytics icon is 'a bit thicker' than the others. Instead I ran the Matched UI Icon Set — Six Cohesive Icons in One Grid prompt on Nano Banana Pro with those six concepts as icon_concepts, 'outline' as the style, my hex code as icon_color, and a white background. Under a minute later I had a 3×2 grid where all six icons shared one stroke weight, plus a one-line note telling me to render them at 24px with a 1.5px stroke. That note is a small thing that saved me a real round-trip with my developer.
The reason I asked for the usage note in the prompt at all comes from a specific past pain. The last time I handed a designer-made icon set to a developer, the icons looked great in the mockup and slightly wrong in the build, because nobody had written down the intended size and the dev guessed. They rendered a 24px icon at 32px, the stroke got chunky relative to the surrounding text, and the whole section looked subtly off in a way nobody could name in standup. The note — exact pixel size, exact stroke weight — closes that gap. It's the difference between 'here are some icons' and 'here are some icons and the spec to implement them correctly,' and the second one is what a real design system hands off.
Why the output actually held together
- All six icons matched stroke weight and corner radius — the thing that's impossible across packs
- Analytics (a bar chart) and Dashboard (a grid) were instantly distinguishable, no labels needed
- No tweaks required — I exported the grid, sliced it, and dropped the icons straight into the page
- The usage note gave me the exact px size and stroke so the CSS matched on the first try
The negative constraint that makes or breaks it
The single most important line in this prompt is 'do not mix outline and filled styles.' Without it, image models hedge — they'll make a couple of icons chunkier or fill one in 'for emphasis,' and suddenly your set has two personalities. Lock the style explicitly and the consistency is remarkable. The 'no labels, no text in the image' line matters too, because the moment a model is allowed to write words it spends its effort garbling 'Integrations' instead of nailing the icon. Forbid the text and it focuses on the shape. The 'each concept recognizable without a label' rule is what keeps you from getting six abstract blobs that all kind of mean 'productivity.'
The honest caveat about generated icons
These are raster icons, not editable SVG paths, and that's the caveat to plan around. For most landing pages it's completely fine — you slice the grid and place each icon, and nobody on the internet has ever inspected your feature section to confirm the icons are 'real vectors.' But if you need to recolor them programmatically with CSS, or animate the strokes on hover, you'll want to trace them into SVG with an auto-tracer or commission the real thing. I tested the auto-trace route on this exact set and the outline style traced cleanly because the strokes were so consistent — the very consistency the prompt enforces is what makes them trace well later. That was an unexpected bonus.
A small workflow that compounds
The reason I run this constantly rather than once is that icon needs recur. Every new feature, every new section, every pricing tier comparison wants its own little cohesive set, and the cost of cohesion across packs never goes down — it's an hour of hunting every single time, forever. Generating the set in under a minute with a locked style turns a recurring tax into a non-event. I keep a tiny text file of my house style — 'outline, 1.5px equivalent, slate blue #3b4a6b, white ground' — and paste it into the prompt unchanged, so even the style decision is already made. The work collapses to listing six nouns. When the section needs a process diagram instead of feature icons, I switch to my Infographic Layout — Process, Comparison, or Timeline in One Card prompt, which handles flow and numbered steps the way this one handles standalone marks. Grab the Matched UI Icon Set — Six Cohesive Icons in One Grid prompt on Prompt Dock and feed it your own six concepts — lock the style, pass your hex code, and stop assembling icons from five different eras at midnight.