Generation Prompts

• Concept model: claude --print — claude-opus-4-8
• Glyph model: claude --print — claude-opus-4-8 (SVG drawn directly, not an image model)
• Format: SVG + ICO + PNG — .svg (source) + .ico (Windows multi-size) + .png (1024x1024 RGBA)
• Rasterizer: cairosvg, each .ico entry rendered from the vector at its own size
• Container: drawn by the generator, not the model — identical across the pack by construction

Pack Prompt

You are a senior icon designer producing a commercial icon pack for Windows desktop and web use — the kind sold on Iconfinder or posted on DeviantArt, not a stock-illustration set.

Design a cohesive pack of 12 icons on the theme: Video Conferencing Apps — Zoom, Teams, Meet, Webex, FaceTime, Jitsi — circle badges.

This step is the concept only. You are not drawing anything yet — a second pass draws each symbol as SVG, and the container shape, the tile gradient, and the final document are generated by code. Your job is to decide what the pack is, who its twelve members are, and what colours it uses.

What a pack is

A pack is one category of similar, nameable things, drawn in one shared visual system. Think "Brave, Chrome, Edge, Firefox, Opera, Safari, Vivaldi" — or "Box, Dropbox, Google Drive, iCloud, Mega, OneDrive" — or "Photoshop, Illustrator, Figma, Canva, Affinity Designer". Twelve members of the same family, each instantly identifiable, all cut from the same cloth.

Name the real things. If the theme is browsers, name the actual browsers. If it is AI coding tools, name Claude Code, Cursor, Copilot, Codex. If it is cloud storage, name the real services. A pack of abstract inventions ("Chroma Bell", "Nebula Cloud", "Prism Home") is a failure — that is not what this is for.

But design an original mark for each. Do NOT reproduce a company's trademarked logo. Take the product's idea — what it does, its colour, its silhouette — and draw a fresh symbol for it in the pack's style. A Dropbox icon is a box or a stack of blue facets; a terminal tool is a prompt caret; a vector editor is a pen nib on a path. The set should feel recognizable at a glance without copying anyone's artwork.

If a theme genuinely has no real-world members (e.g. "Website Page Icons — Cart, Checkout, Orders"), then the 12 members are the concrete pages or functions themselves, still named plainly.

The shared visual system

Pick ONE container shape for the whole pack. The renderer draws it for you, identically on all twelve — you only choose which one fits the theme:

Colour

The pack is two-tone by design, and that is what makes it read as a set:

• Each icon gets its own tile_color — the container behind it. This is where a member's identity lives: Firefox orange, Dropbox blue, Spotify green. Pick a saturated, distinguishable hex per icon; no two should be near-identical, and all twelve should look like one palette family rather than a random assortment.
• The whole pack shares ONE glyph_color — the symbol drawn on top of every tile. Almost always #FFFFFF; use a very dark neutral (e.g. #1A1A22) only if the pack's tiles are all pale.
• For a bare-glyph pack there is no tile, so tile_color becomes the symbol's own colour and glyph_color is ignored.

Every colour must be a plain 6-digit hex string like #3B82F6.

Describing each symbol

Each icon's glyph_brief is an instruction to whoever draws it, in flat geometric terms — what shapes, in what arrangement. "A rounded upward chevron over a horizontal baseline bar" is useful; "a beautiful modern representation of growth" is not. Keep every brief phrased the same way and at the same level of detail, so the twelve come out at one optical weight.

Two hard constraints on what you may ask for, because the drawing pass is validated against them:

• No lettering. The renderer has no fonts. If a member is best known by a letter, describe the letterform as geometry ("two vertical bars joined by a crossbar") or pick a non-letter symbol instead.
• One colour per symbol. The symbol is drawn in the pack's single glyph_color, with transparency as the only available second shade. Do not ask for a multi-colour symbol.

Return a JSON object

• "title" — a catchy name for the pack.
• "slug" — a kebab-case slug.
• "description" — 2-3 sentences on the pack's style and what it is for.
• "introduction" — a short intro paragraph for the pack's documentation.
• "metadata":
  • "style" — the visual style in a few words (e.g. "Flat vector, solid fills, single-weight symbols").
  • "container" — exactly one of: squircle-tile, folder-tab, circle-badge, rounded-square, drive-block, bare-glyph.
  • "glyph_color" — the one hex colour every symbol is drawn in.
  • "palette" — the tile colour family in a phrase (e.g. "saturated brand hues, one per member").
  • "keywords" — a list of 5 keywords.
• "icons" — a list of 12 objects, each with:
  • "name" — the thing itself, named plainly ("Firefox", "Google Drive", "Checkout").
  • "concept" — one line on what the symbol shows and why it reads as that thing.
  • "glyph_brief" — the flat geometric description of this one symbol, per the section above.
  • "tile_color" — this icon's container hex.
• "caption" — a short notification caption (e.g. "12 flat-vector browser icons in SVG, ICO and PNG.").

Return the JSON object and nothing else.

Drawing Contract (the glyph call)

You are drawing the SYMBOLS for a cohesive icon pack as SVG.

Pack: Round Table — Video Call Badges
Theme: Video Conferencing Apps — Zoom, Teams, Meet, Webex, FaceTime, Jitsi — circle badges
Style: Flat vector, solid white fills, single-weight geometric symbols on colour discs
Container: every icon is placed by our renderer inside a perfect circle badge. YOU DO NOT DRAW THE CONTAINER, the tile, the background, or any border — those already exist. Draw only the symbol that sits inside.

## Rules — these are enforced by a validator, not by review

1. Draw each symbol in a plain square coordinate box from 0,0 to 100,100. Use the whole box; our renderer scales and centers it into the container for you.
2. Output BARE SVG shape elements only: `<path>`, `<circle>`, `<rect>`, `<ellipse>`, `<polygon>`, `<polyline>`, `<line>`, `<g>`. No `<svg>` wrapper, no XML declaration, no comments, no markdown fences.
3. **No `<text>` or `<tspan>`, ever.** The rasterizer has no fonts — a text element renders as nothing. If an icon needs a letterform, draw the letter as filled `<path>`/`<rect>` geometry.
4. No `<image>`, `<script>`, `<style>`, `<foreignObject>`, and no `href`/`src` pointing anywhere external. Nothing may be fetched at render time.
5. Colour: the symbol's default fill is already set to `#FFFFFF` by the renderer, so plain shapes need no fill attribute. You MAY set `fill="#FFFFFF"` explicitly, or use `fill-opacity` between 0.35 and 0.75 for a secondary shade. Do not introduce any other colour — one symbol colour plus its own transparency is what makes the pack read as a set.
6. Prefer solid filled shapes over strokes. If you do stroke, use `stroke="#FFFFFF"` with `stroke-width` between 6 and 9, plus `stroke-linecap="round"` and `stroke-linejoin="round"` — and use the SAME stroke width on every icon in the pack.
7. One optical weight across all twelve. Same visual density, same corner treatment, same level of detail. This is the single most important property of the set.

## Output format

For each icon, one delimiter line then its markup, nothing else:

=== ICON: <slug> ===
<path d="..."/>

Emit all 12 icons, in the order listed, using exactly the slugs given.

## The icons

- `zoom` — **Zoom**: A solid horizontal rounded rectangle with corner radius about 20% of its height, set slightly left of centre. Attached to its right edge is a solid right-pointing trapezoid lens hood, narrow where it meets the body and widening outward, with rounded outer corners. The whole shape is centred optically in the badge and fills about 55% of the badge width.
- `microsoft-teams` — **Microsoft Teams**: Two simple person figures, each a solid circle head above a solid rounded-top half-capsule body. The front figure sits left of centre and is about 25% larger. The rear figure sits up and to the right, partly hidden behind the front one, and is drawn at 60% opacity. A thin gap the colour of the badge separates the front figure's outline from the rear figure.
- `google-meet` — **Google Meet**: A solid rounded rectangle camera body, with the top-left corner cut off at 45 degrees to form a small chamfer. On the right is a solid right-pointing triangular wedge with rounded tips, separated from the body by a narrow vertical gap the colour of the badge. The body and wedge together are centred and span about 55% of the badge width.
- `webex` — **Webex**: Two thick, open, C-shaped arcs of equal stroke weight with round caps. The left arc opens to the right and the right arc opens to the left. They overlap at the centre, and the right arc is drawn at 70% opacity where it passes over the left one. Together they form a horizontal chain-link shape about 60% of the badge width.
- `facetime` — **FaceTime**: A solid square with rounded corners (radius about 25% of its side), placed left of centre. A solid circle about 35% of the square's width is punched out of its centre as a transparent cutout, showing the badge colour through it. On the right is a short solid trapezoid lens hood that widens outward. The whole shape spans about 55% of the badge width.
- `jitsi-meet` — **Jitsi Meet**: A solid rounded-rectangle speech balloon with a small triangular tail at the bottom-left corner. Inside, cut out as transparent negative space, are two chevrons facing away from each other: a left-pointing chevron on the left and a right-pointing chevron on the right, with an empty gap between them. The balloon fills about 60% of the badge width.
- `goto-meeting` — **GoTo Meeting**: A thick open circular ring with round caps, drawn about 300 degrees round with the gap on the right side. Through the gap, a solid arrow points to the right: a straight horizontal shaft from the ring's centre that ends in a triangular arrowhead just past the ring's outer edge. Ring stroke and shaft have equal weight.
- `whereby` — **Whereby**: A tall rectangular door frame drawn as a thick outline with a rounded top edge and an open bottom that rests on a short horizontal floor bar. Inside the frame, a solid door panel is swung open toward the viewer. It is drawn as a parallelogram hinged on the left edge of the frame and shown at 70% opacity. The frame is centred and about 50% of the badge height.
- `discord` — **Discord**: An over-ear headset: a thick semicircular headband arc with round caps across the top, ending at two solid vertical rounded-rectangle ear cups. A short curved microphone boom runs from the bottom of the left cup toward the bottom centre and ends in a small solid circle. Headband stroke weight matches the pack's standard stroke.
- `slack-huddles` — **Slack Huddles**: A solid speech balloon shaped like a wide rounded rectangle, with a small rounded tail at the bottom-right. Inside, three equal solid circles sit in a horizontal row across the middle and are cut out as transparent negative space. Above the middle circle, a short thick arc with round caps is also cut out, suggesting a headphone band over the group.
- `zoho-meeting` — **Zoho Meeting**: A solid horizontal rounded rectangle screen sitting on a short vertical stand stem and a wider horizontal base bar. Centred inside the screen, a right-pointing triangle with rounded corners is cut out as transparent negative space. The screen spans about 60% of the badge width.
- `bigbluebutton` — **BigBlueButton**: A thick outlined circle ring about 60% of the badge width. Inside it, separated by a gap the colour of the badge, sits a smaller solid circle. On the solid circle, a short horizontal crescent highlight near the upper-left is cut out as transparent negative space, so it reads as a domed button. Below the ring, a short horizontal bar at 60% opacity acts as a shadow line.