Custom Icons

Build each icon through an inspectable source-to-asset pipeline. Treat the user's stated subject, style, palette, format, dimensions, and destination as the asset contract.

Workflow

1. Establish the asset contract

Inspect the request, supplied references, and target project before asking questions. Infer routine details with these defaults:

• Match a supplied reference or existing icon set before introducing a new style.
• Choose SVG for monochrome silhouettes, line art, and simple UI artwork.
• Choose transparent PNG or lossless WebP for 3D, multicolor, shaded, or textured artwork.
• Use a square 24×24 coordinate system for unspecified UI SVGs and 1024×1024 for unspecified detailed illustrative SVGs.
• Use black for an unspecified vector color and preserve the generated/source dimensions for an unspecified raster size.
• Save final assets in the request workspace when no destination is given.

Ask one concise question only when the subject is missing, requirements conflict, or the format choice would materially change the requested appearance. A target framework is optional unless implementation or framework-specific packaging is requested.