Mark Otto details Pierre's 1,200-plus custom icons redrawn at three sizes
Mark Otto details 1,200-plus icons for Pierre, redrawn at 12, 16 and 24 pixels without AI assistance. Custom Figma plugins, React exports and a preview app support the icon system.

TL;DR
- Pierre’s new library spans 1,200-plus icons across three sizes; its designer, Mark Otto, detailed the months-long project in his announcement.
- Every icon’s vector artwork was drawn without AI assistance. AI helped with scripting and custom plugins, Otto said in a reply.
- Reusable Figma components, SVG and React exporters, and independently styleable foreground/background layers underpin the system, according to his feature rundown.
Otto abandoned runtime icon composition after it roughly doubled the gzipped size of two examples. His arrow-tapering plugin tackles the heavy spot where strokes converge, but didn’t make the first beta.
Three hand-drawn sizes
Otto redrew icons at 12, 16 and 24 pixels, adjusting detail and optical weight for each size. At 24px, locks gain keyholes and buildings get additional windows.
His design breakdown gives the stroke specifications:
| Icon size | Old 1.5px stroke, scaled | New default stroke | Heavier stroke for most filled line symbols |
|---|---:|---:|---:|
| 12px | 1.125px | 1px | 1.25px |
| 16px | 1.5px | 1.25px | 1.5px |
| 24px | 2.25px | 2px | 2.5px |
Figma variables hold those weights, letting Otto adjust an entire size without editing hundreds of vectors individually. Icons support up to three variants: outline, fill and duo.
Reusable layers and masks
Related icons share components rather than separate copies of every shape. A badged icon combines three pieces:
- Base shape: the file, folder or other container.
- Knockout mask: space removed from the base so the badge remains legible.
- Badge: the symbol placed on top.
Otto kept Figma’s unions and subtractions non-destructive. Changing the shared file shape can consequently update 20 related icons automatically.
AI-built Figma plugins
Otto used AI to build supporting tools while drawing the artwork himself. His plugin write-up records both the shortcuts and the experiments he left out:
- Layer Swap: replaces nested components across selected icon sets, matching size and style properties. It also rotates or flips a layer across every variant around that layer’s own center.
- Shape Language Overlay: places size-matched reference shapes in locked sibling frames without modifying exportable components. Otto barely used it because the extra frames cluttered his workspace.
- Taper Stroke: splits a vector network into editable strokes and narrows them toward a junction while preserving the outside silhouette. Figma’s native variable-width tool couldn’t handle his combined arrow vectors as needed. He deferred the plugin’s output from the first beta while deciding how to integrate it.
- Icon Preview Grid: generated with Figma’s AI tools, this plugin arranged selected icons into grids and lists for the article’s illustrations.
- Export and cleanup tools: his broader toolkit also included SVG and React exporters and a boolean de-constructor.
React composition’s bundle cost
Otto tried carrying Figma’s component hierarchy into React through calls such as:
That tidy API came with an ugly bundle bill. His comparison reported:
| Example | Composed component, gzip | Individual icon, gzip |
|---|---:|---:|
| File with a badge | 2.81KB | 1.40KB |
| Folder with a badge | 2.88KB | 1.36KB |
Geometry introduced another problem: flattening booleans could shift instances by a pixel, while artwork outside a 16px frame could enlarge the exported viewBox and make the rendered icon shrink.
Otto retained composition in Figma and returned to individual icons for React. Fixed viewBoxes and visible overflow preserve the intended sizing without clipping artwork that extends beyond the frame.
Canonical SVGs and preview checks
The final handoff separates visual editing from code generation: Figma owns the artwork, and the repository owns processing. The export workflow runs through three checkpoints:
- Export: the SVGO Exporter writes canonical SVGs and a
manifest.jsonfrom the drawn variants. - Review:
REPORT.mdflags missing artwork, duplicates and alignment problems. - Generate:
npm run iconsproduces React components, sprite outputs and previews.
Deterministic foreground/background classes support separate styling of those layers, as Otto noted in his overview. A custom preview app supports visual checks, including icons in isolation and in product-like lists.
Pierre also maintains an Apache-2.0 repository containing source SVGs and compiled React components.