axi-designv1.50.0

Reference

Icons

Every glyph is drawn to rule 12: a 24 canvas, a 3px stroke in currentColor, mitered joins, square corners, and no angle that is not 0°, 45° or 90°. Size one with --axi-icon-size; it takes its ink from whatever it sits in.

The vocabulary — which shapes mean what, and what they are called — derives from Lucide, used under the ISC licence. No path data is Lucide's; every drawing is this language's own.

Point a <use> at the sprite and the glyph inherits the ink around it:

<svg class="axi-icon"><use href="node_modules/@axiapps/axi-design/dist/icons/sprite.svg#axi-search"/></svg>

That is a cross-document reference, so it is same-origin: over http(s) it works and the glyph inherits the ink around it, but under file:// — an Electron window opened with loadFile() — it resolves to nothing and the icon is silently absent. There, inline the sprite into the document once and reference bare fragments (#axi-search), or use the standalone dist/icons/<name>.svg files.

This site takes the inlining route on every page, which is why the markup below says #axi-search with no file part.

When the set does not have it

The suite imports 165 distinct Lucide names. This set is 57 drawings and answers 47 of them; it will realistically reach sixty or seventy — so an app importing from lucide-react and from here is the expected arrangement, not a failure of the migration. The vocabulary was always borrowed; only the drawings are ours. Port what this set answers, leave the rest on Lucide, and do not re-decide it app by app.

Some names this set answers under a different one. Those resolve in the sprite, so the port is a rename:

<svg class="axi-icon"><use href="#axi-triangle-alert"/></svg>

And some it will not draw at all, because the shape needs a curve this grammar does not have. Those need a decision, and here it is:

Lucide nameUseWhy
starcrown, or a filled .axi-diamond Five points need 36° and 72°. The four-point substitute cannot have concave vertices closer in than R/√2 — which is an octagon — so it comes out a lumpy diamond. Use crown where it means featured or best, and the diamond where it means rating.
sparklescrown The same floor by another route. A four-armed twinkle with equal arms reads as plus, with unequal arms as a dagger, and with eight arms it closes into a solid octagon at 3px. Three drawings, none of them the word.
circlesquare A circle is the one boundary this grammar has decided not to draw. It resolves in the sprite as an alias.
triangle-alertcircle-alert Not an absence — a duplicate. A 45°-only isoceles triangle is forced to 2:1 tall-to-wide, which is a spike rather than a warning sign, and the eight-sided room already is the warning sign. It resolves in the sprite as an alias.
anything elsestay on Lucide If the metaphor needs a curve and neither a square nor a diamond says it, an absent glyph beats a wrong one. Open an issue describing what the shape needed.

Drawing a new icon

  1. Find the metaphor in Lucide and keep its name.
  2. Re-draw it on the 24 canvas: 3px stroke, mitered joins, butt caps, everything inset 1.5 from the edge. A circle becomes a diamond if it is a node — a lens, a head, a dot — and a square if it is a boundary. Every angle is 0°, 45° or 90°.
  3. Put axis-aligned strokes on an odd half-integer (3.5, 6.5…), or on 12 if the glyph is built around its centre line.
  4. Save it as icons/<name>.svg and add a row to docs/manifest/icons.mjs with its categories, aliases and keywords.
  5. Run npx vitest run tests/icons.test.mjs. It checks all of the above. If it fails, the drawing is wrong — not the check.
  6. Run npm run build to regenerate the sprite, and commit the drawing with its artifact.

If the metaphor genuinely needs a curve and neither a square nor a diamond says it, do not ship it. A wrong glyph costs more than an absent one — the table above lists what this set has refused and what to reach for instead. Open an issue describing what the shape needed.