Skip to content
Concepts

Concepts

Fungi's approved illustrated symbols and visual studies

Sigils provides decorative SVG marks for Fungi interfaces. Its gallery shows the marks alongside reference artwork and visual studies, so consumers can check which drawings are approved, live, or still concepts.

The public component accepts a SigilName and an optional pixel size. isSigilName checks whether a string is one of the package’s available names; it does not check whether using that mark is approved for a particular action or permission.

The workbench separates the library, families, use cases, source references, and curve review. Its Permission Use page is a visual study, not the shipped permission screen. An SVG’s presence in the package does not grant a capability or imply that an interface uses it.

Sigils use Stipe’s illustration roles through inline SVG styles, with literal fallbacks when Stipe is absent. Themes may retint --stipe-art-* roles. Page figures, emphasis rays, generation art and completion swooshes use --stipe-sketch-ink on light themes and retain art cream on dark themes. Figure eyes use --color-base-100, so they read as cut-outs. List and Prints paper and cream details on coloured shapes retain --stipe-art-cream in both appearances. There are no separate --sigil-figure* hooks.

The workbench loads Stipe through Tailwind. Its theme toggle switches latte and mocha; the gallery follows it by default, with optional explicit canvas themes. The Themes story compares latte, field-guide, consulting, mocha and field-guide-night at 64, 28, 20 and 16 pixels, including the Tourtois disabled filter. Palette defaults and theme ownership live in Stipe, not in this package.

Run pnpm run build, pnpm run pack and pnpm run stranger in this package. The maintained stranger proof installs only package tarballs into a fresh npm consumer, checks the exact shipped files, runs the public runtime fixture and compiles every JavaScript entrypoint with strict NodeNext and no library-check skip. This qualification does not publish npm releases or push a repository split.

See LICENSE for the license and the package manifest for its public repository destination.