wand-kit 0.0.0-stage → 0.2.0

package/PROMPT.md

@@ -0,0 +1,255 @@
+# Wand Power Prompt — Studio (v0.1)
+
+One design surface for every material a sales or marketing team needs, on
+either Wand brand. The page is HTML; it is composed from a component library on
+brand tokens; Chromium renders it; every gate measures that render; and every
+export (PDF, PNG, PowerPoint, a one-file HTML) is read from it, so nothing can
+drift from what was reviewed on screen.
+
+This document is the design system and the pipeline, and the source of truth
+on every design question. `brand/BRAND.md` and `brand-next/BRAND.md` win on
+values (a hex, a face, an asset); `STATUS.md` is state; `SKILL.md` is procedure.
+
+**Why this exists.** The outputs that reviewed best in October 2026 (the
+Franklin Templeton case study, the aviation overview, the BofA talk) were all
+hand-written HTML outside the kits: brand fonts and art through `brand.js`, a
+palette, free composition, two gates. The form-filling kits (44 slide layouts,
+26 document blocks) guaranteed correctness and could not supply composition.
+This kit keeps the freedom and systematises the rest: tokens, surfaces,
+components, gates, exports.
+
+---
+
+## 0. Ground truth
+
+Two brands, one component set.
+
+| Brand | Directory | Faces | Guideline |
+|---|---|---|---|
+| `current` | `brand/` | Geist | the Kearney leadership deck; `brand/BRAND.md` |
+| `next` | `brand-next/` | FK Roman Standard Light, Overused Grotesk | the website, read 2026-10-05; `brand-next/BRAND.md` |
+
+Each directory's `tokens.json` carries the brand as values a kit can draw with:
+`swatch` (the measured hexes), `roles` (what each value is for, once per
+ground), `faces` (the files and their PowerPoint names), `shape` (radius,
+strokes) and `art` (which file plays which role). A component asks for a role
+(`--ink`, `--accent`, `--emph`) and never for a hex. Where a hex in
+`tokens.json` and `BRAND.md` differ, `BRAND.md` is right and `tokens.json` has
+drifted.
+
+`current` is the default while the two overlap; a job is on `next` when the
+user asks for the new brand. The default is one constant, `DEFAULT_BRAND` in
+`kit/lib/brand.js`, and `doctor` prints the rule from it. The FK Roman
+Standard licence for documents is still to be confirmed
+(`brand-next/fonts/LICENSE-FONTS.md`).
+
+## 1. Surfaces — locked
+
+A surface fixes the frame, the margins, where the chrome sits, the type scale
+and the minimum type size. Nothing else. `kit/lib/surfaces.js` is the table.
+
+| Surface | Canvas (px) | Content box | Base | Min type | For |
+|---|---|---|---|---|---|
+| `letter` | 816 × 1056 | 60 / 92 / 60 / 74 | 11.6px | 7px | documents, one- and two-pagers, case studies |
+| `a4` | 794 × 1123 | as letter | 11.6px | 7px | the same, for Europe |
+| `slide` | 1920 × 1080 | 72 / 178 / 72 / 112 | 21px | 13px | decks, talks |
+| `square` | 1080 × 1080 | 72 / 150 / 72 / 120 | 22px | 14px | social cards |
+| `og` | 1200 × 630 | 64 / 120 / 64 / 90 | 20px | 13px | link previews, banners |
+
+The letter scale is the Franklin Templeton letter's; the slide scale is its
+deck's. A letter page is read at 96 px/in, a slide at 192 px/in (10 in wide).
+
+**Chrome on every page:** the tag and eyebrow top left (`TAG | Section`), the
+mark top right, the footer with the running line and the page number. A page
+may drop it (`chrome: false`) only on a social card.
+
+## 2. Colour
+
+Roles, per ground. A page is `light` or `dark`; the same role names resolve to
+the ground's values, so one component draws on both.
+
+| Role | Light (current) | Dark (current) | Use |
+|---|---|---|---|
+| `bg` | F8F6FB | 240F48 | the ground |
+| `paper` | FFFFFF | 291D5A | cards, nodes, chips |
+| `ink` | 1D1A33 | FFFFFF | titles, values |
+| `text` | 5C5779 | F5F5F5 | running text |
+| `soft` / `muted` | 555077 / 999999 | BBBBBB / 746B98 | small print / chrome |
+| `accent` | 8B7CF6 | 9481FF | anything drawn: meters, dots, arrows |
+| `accentText` | 6C5CE7 | 9481FF | the accent phrase in a title, outcomes, deltas |
+| `label` | 6C5CE7 | A78BFA | tags, section numbers |
+| `emph` / `emphInk` / `emphText` / `emphAccent` | 251C63 / FFF / DCD6F5 / AA9BFF | 4D2E8C / FFF / DCD6F5 / C4B5F4 | the emphasis card and what sits on it |
+| `stroke` / `rule` / `track` / `surface` | E4E0F2 / E4E0F2 / E9E6F5 / EBE8F8 | 5B4BB0 / 3A2E63 / 1A1033 / 1A1033 | card strokes, hairlines, meter tracks, tiles |
+
+The next brand fills the same roles from the website (gold the one accent,
+violets as grounds, beige as paper); see `brand-next/tokens.json`.
+
+**Rules.**
+- One accent. The accent phrase in a title is the single most recognisable
+  device in the system: one per title, never two, the sentence period in ink.
+- One emphasis card per row, at most one or two per page.
+- Light pages carry no art. Dark pages carry art on the cover, the closing and
+  a statement; a dark content page is flat.
+- A job may declare a client's own colours as a `theme` (role overrides and
+  `extra` hexes). The brand gate then reports them as declared, so a client
+  look is a decision on record rather than a hex that slipped in.
+
+## 3. Typography
+
+Three face roles per brand: `display` (titles, figures, the lockup), `body`
+(everything read), `label` (tags, eyebrows, table heads, chips' numerals).
+Tracking and leading travel with the face in `tokens.json`; the CSS sets them
+from the same values.
+
+| Role | current | next |
+|---|---|---|
+| display | Geist SemiBold, −0.02em | FK Roman Standard Light, −0.07em, 1.06 |
+| body | Geist Regular | Overused Grotesk, −0.02em |
+| label | Geist SemiBold, +0.18em, caps | FK Roman Standard Light, caps |
+
+**Weight carries no hierarchy on the next brand** (the serif ships one weight);
+the face does. Components therefore never rely on bold to separate levels, and
+`strong` is 600 on the body face only.
+
+**The scale is the surface's** (`--t-h1` … `--t-note`), so a component sets
+`font-size: var(--t-h3)` and lands right on every surface. Nothing under the
+surface's minimum; the type gate fails the build otherwise.
+
+Figures are tabular (`font-variant-numeric: tabular-nums` on the page).
+
+## 4. Chrome
+
+Drawn by `c.page()` on every page: eyebrow (`job.tag | eyebrow`), mark, footer
+(`job.footer`, page number). The cover and closing pages are `c.cover()` and
+`c.closing()`, which place the brand art and the lockup; a job gives them
+words, never styling. Every piece of chrome is `.deco` or chrome-classed, so
+the gates know what is content and what is frame.
+
+## 5. Catalog
+
+The components (`node wand.js components`; `kit/lib/components.js`):
+
+| Component | For |
+|---|---|
+| `page`, `cover`, `closing` | the three page kinds |
+| `sec(num, title)` | a numbered section heading; the title carries the accent phrase |
+| `lead`, `body`, `small`, `note`, `tag` | the type roles |
+| `cols(n, items)` | a grid of 2 to 5, or `12` / `21` for a 1.35 : 1 split |
+| `card({ tag, title, body, out, emph })` | the card, the emphasis card, the function card with its outcome line |
+| `strip(labels, { on })`, `chip`, `phase(i, label, line)` | the journey: numbered chips with arrows, the chip-then-heading row |
+| `flow({ label, nodes, note })` | the five-node tool-vs-labor flow |
+| `table({ head, rows, emph })` | ruled tables; a cell with `meter: true` draws its bar |
+| `quote({ text, by, emph })`, `who` | testimonial cards, name over role, no photographs |
+| `stats`, `delta(from, to)` | figures, before-and-after |
+| `steps(items)` | next steps with arrows |
+| `callout`, `list`, `chapter`, `img`, `icon`, `tile` | the rest |
+
+**Composition is free.** A job writes the markup it needs from these, adds its
+own CSS on top (custom properties only) and may write raw markup where no
+component fits. Recipes, not forms: `templates/` and `examples/` are starting
+points to copy from, not fields to fill. The things the catalogue does not
+decide, and that make or break a page:
+
+- **An argument per page.** Before any markup, one line per page saying what
+  the page claims. A document that passes every gate and "spreads information
+  with no story" (the aviation round-1 verdict) fails here.
+- **Three sections a page, not four.** The cramped first pass of the aviation
+  overview had four; the accepted one had three.
+- **Separate with alignment, hairlines and type, not boxes.** Cards are for
+  things that are a set (layers, functions, steps); running text sits on the
+  ground.
+- **Short lines in cards.** One sentence and an outcome. The card's body is
+  never the place for the argument.
+- **Equal heights in a row** (`stretch`), titles at one height, and the empty
+  space at the foot of a page shared by its sections, never left under one.
+
+## 6. Pipeline
+
+```
+new ─▶ argue ─▶ content ─▶ compose ─▶ build ─▶ review ─▶ ship
+```
+
+1. **new** — `node wand.js new <dir> --surface letter --brand current`. A job
+   folder: `job.mjs`, `content.txt`.
+2. **argue** — the page list with one claim per page, in the chat, before any
+   markup. For a rebuild, the mapping from source pages to it.
+3. **content** — for a rebuild, the source's strings into `content.txt`, one
+   per line, verbatim (`tools/extract.py` from the decks or docs kit, or
+   `pdftotext`). Every departure declared in `edits`; every line left out in
+   `cut`. For authored copy, no file.
+4. **compose** — `pages(c)`. Lines by number (`c.L(12)`), components, job CSS.
+5. **build** — `node wand.js build <job>`: the gates (§7), then the PDF, a PNG
+   per page, the contact sheet. `watch` does this on every save in under a
+   second with the browser kept warm.
+6. **review** — look at `out/sheet.png`, then at any page the gates named.
+   Read the pages as the reader will: does each carry its claim?
+7. **ship** — `node wand.js ship <job> [--pptx]`: the build, the one-file HTML,
+   the PowerPoint. The review note says what was changed from the source and
+   why, which gates ran, and what a human still has to decide.
+
+## 7. Gates — every build, every job
+
+| Gate | Fails when | Blind to |
+|---|---|---|
+| fit | anything in the content box runs past it, under the footer, or off the sides | a page that fits and reads badly |
+| coverage | a line of `content.txt` is not on the page (whole, or in its declared parts), less the `cut` lines | a line that is present and in the wrong place |
+| overlap | one text box sits on another | text on art |
+| brand | a computed colour, border or fill that is not a token or a declared theme colour | gradients and images |
+| fonts | a text run not in the brand's faces | a weight the face lacks (the browser synthesises) |
+| type | text under the surface's minimum size | |
+| dashes | an em dash reaches a page (JP Sacy, Oct 2026: a GPT marker) | |
+| names | a denied name (a previous client's) is on a page | |
+| pdf text | the PDF's text misses a line, or carries an em dash | |
+| contrast (warn) | text under WCAG AA against its background, chrome excepted | |
+| measure (warn) | a paragraph over the surface's characters-per-line | |
+| console | a page error | |
+
+The gates read the DOM Chromium laid out for the PDF; nothing is inferred from
+the spec. What no gate sees: the argument, the pacing, and whether the right
+component was chosen. That is the review.
+
+## 8. Content rules
+
+- **Verbatim for a rebuild.** Reflowing is fine; rewording is not. Every
+  departure is an `edit` with the needle and the replacement, so the review
+  note can list it and coverage still passes.
+- **No em dashes** in anything generated: a comma or a semicolon, a colon
+  before a list. For a source that has them, declare the swaps as edits.
+- **No photographs of people** in sales material without consent on file. The
+  `quote` component sets name over role and nothing else.
+- **A client's confidential detail** (a vendor they use, a figure they have not
+  published) does not travel into a generic piece. The `denylist` catches a
+  name; the review catches the rest.
+- **Figures are sourced on the day** and dated on the page.
+
+## 9. Environment gotchas
+
+- **The browser.** The kit renders with Chromium. `findChrome()` looks at
+  `WAND_CHROME`, Playwright's own cache, then the system. In a sandbox without
+  one, `doctor` says so and nothing renders: there is no browser-free fallback
+  in this kit.
+- **LibreOffice** substitutes faces and widens text; it is a geometry check for
+  the PowerPoint export, never a judge of fit.
+- **Google Slides and Keynote** ignore embedded fonts; the `.pptx` needs the
+  faces installed there.
+- **iCloud** evicts files under `Documents/`; a build that hangs on a font is
+  usually that.
+
+## 10. Known drift — don't propagate
+
+- `brand/BRAND.md` keeps values in prose and `wand_kit.js` keeps a copy; this
+  kit reads `brand/tokens.json`, added 2026-10-16 from the same values.
+- The Franklin Templeton case study shipped on colours sampled from the
+  client's own slides, not the brand's. Its studio regression declares them as
+  a theme; nothing in the components carries them.
+
+## 11. Open items
+
+1. **DOCX export.** Declined for now: Word cannot hold these pages. If needed,
+   a semantic export (headings, prose, tables) as an editable-text version,
+   labelled as such.
+2. **The sandbox's browser.** Confirm Chromium is present where sellers work
+   before the kit replaces `decks` and `docs`.
+3. **The chapter panel and the talk runtime** (presenter view, demos) from the
+   BofA deck: carry into the slide surface when a talk needs them.
+4. **Email and banner surfaces**: declared in §1's spirit, not yet in the table.

package/SKILL.md

@@ -0,0 +1,117 @@
+---
+name: wand-design
+description: Rebrand or create Wand material on the current or the new brand - decks, documents, one-pagers, case studies, social cards. Use when a .pptx, .docx or .pdf is attached, or branded work is wanted.
+compatibility: Requires Node.js 18+, code execution enabled in claude.ai (Settings > Features), and a Chromium the kit can find (Playwright's cache or the system). No network needed once installed. Python 3 embeds fonts in the .pptx; without it the deck ships with the faces named, not embedded.
+license: Proprietary - Wand AI
+metadata:
+  version: "0.2.0"
+---
+
+
+# Wand design
+
+## First: find the kit and stand in it
+
+1. **Installed from npm** (the usual way): it is at `node_modules/wand-kit/`.
+   If it is not there yet: `npm install wand-kit@latest --no-audit --no-fund`.
+2. **Attached to the chat as a zip**: unzip it and enter the folder it makes.
+3. **You are already inside it**: `wand.js` is next to this file.
+
+Then:
+
+```bash
+node wand.js doctor
+```
+
+Every row must be clear, and `chromium` must name a binary. If it does not,
+**stop and say so**: nothing renders without a browser, and never report checks
+you did not run. Every path below is relative to the kit folder.
+
+## What this is
+
+One HTML page per slide, sheet or card, composed from a component library on
+the brand's tokens; Chromium renders it; every gate measures that render; the
+PDF, the PNGs, the PowerPoint and the one-file HTML are all read from it.
+`PROMPT.md` is the design system: read it once for design decisions, not per
+page. `node wand.js components` lists the vocabulary.
+
+## Which brand
+
+Two brands, one kit: `current` (Geist) and `next` (the website's). `doctor`
+ends with the brand rule: which one is the default, and the words that ask
+for the other. Follow it as printed. When the user names no brand, build on
+the default without asking; when their words ask for the other, pass
+`--brand` to `new`. One brand per piece, never a mix, and the review note
+says which. The rule lives in the kit, not here, so it can change without
+anyone reinstalling the skill.
+
+## Read only what the job needs
+
+| Job | Read |
+|---|---|
+| A document, a two-pager, a case study | `PROMPT.md` §5 and `templates/page.mjs`; `examples/overview/job.mjs` for a finished one |
+| A deck or a talk | §5 and `templates/slide.mjs` |
+| Social cards, a banner | `templates/card.mjs` |
+| Edit a job this kit built | the job's `job.mjs` only, then `build` |
+
+## The jobs
+
+### Rebuild from a source they attached (a .pptx, .docx, .pdf, .html)
+
+1. Dump the source's strings verbatim, one per line, into `content.txt`:
+   `pdftotext -layout` for a PDF; for a .pptx or .docx, unzip and read the XML
+   text runs in order, or use the decks kit's `tools/extract.py` if present.
+2. **Write the page list in the chat before any markup**: one line per page
+   with the claim it carries and which source lines it takes. Then compose.
+3. `node wand.js new work/<name> --surface letter|slide` (plus `--brand` only
+   when the brand rule says so), write `pages(c)` with `c.L(n)` for every string, declare every departure
+   in `edits` (no em dashes: swap them for commas or semicolons there) and
+   every line left out in `cut`.
+4. `node wand.js build work/<name>/job.mjs` until every hard gate is ok. Look
+   at `out/sheet.png`. Open a page only where something looks off.
+5. `node wand.js ship work/<name>/job.mjs --pptx` for a deck; without `--pptx`
+   for a document. Deliver the PDF (and the .pptx, and the .html) with the
+   review note.
+
+### Author from a brief
+
+Skip `content.txt` (delete the `content:` line in the job). Write the page list
+with its claims first, then the pages. Coverage is skipped and says so; the
+review reads the argument instead. Three sections a page, not four.
+
+### Make it generic (an industry version of a client piece)
+
+Author from the client piece: remove the client's figures, names, quotes and
+vendors; put the client's name and its people in `denylist` so the gate proves
+they are gone. Say in the note what was cut and what was generalised.
+
+### Social cards
+
+`--surface square` or `og`; one `c.page()` per card; `out/pages/pNN.png` are
+the deliverables.
+
+### Older Wand work
+
+A deck or document made before this kit has no `job.mjs`. Treat it as a
+source and rebuild it (the first job above), on the brand the rule gives.
+One exception: a small edit (a date, a word, a figure) to a deck the old
+decks kit built, where they want the file otherwise untouched. For that edit
+only, `npm install wand-decks-kit@0.11.0 --no-audit --no-fund` and follow
+that kit's SKILL.md on editing (`node wand.js show`, then `edit --set`).
+An older copy of this skill may describe that kit, a routing table between
+two kits, or `edit --set`; none of it applies to anything else.
+
+## The review note, always
+
+Which brand it is on; what was changed from the source and why (every edit,
+every cut); the gate table as printed; what a human still has to decide (a figure to confirm, a
+quote to clear, a claim legal should see). A file delivered without the gate
+table has been checked by nobody.
+
+## Available scripts
+
+- **`wand.js`** — doctor, new, build, check, ship, watch, gallery, components, brands
+- **`lib/engine.js`** — the render and the gates
+- **`lib/components.js`** — the vocabulary and its CSS
+- **`lib/pptx.js`**, **`tools/embed_fonts.py`** — the PowerPoint export
+- **`lib/html_export.js`** — the one-file HTML with its runtime

package/START-HERE.md

@@ -0,0 +1,16 @@
+# Wand studio — start here
+
+```bash
+node wand.js doctor                                   # what works here; chromium must name a binary
+node wand.js new work/acme --surface letter            # the default brand; doctor prints the rule
+#   write work/acme/job.mjs (pages(c)) and, for a rebuild, work/acme/content.txt
+node wand.js build work/acme/job.mjs                  # gates, PDF, a PNG per page, out/sheet.png
+node wand.js ship  work/acme/job.mjs --pptx           # + one-file HTML, PowerPoint
+```
+
+`node wand.js components` lists the vocabulary; `examples/overview/job.mjs` is
+a finished document and `examples/gallery/job.mjs` every component on one
+sheet (`node wand.js gallery --brand next` draws it on the website's brand).
+
+`PROMPT.md` is the design system. `SKILL.md` is the procedure. Read §5 of the
+prompt before composing; everything else when a gate names it.

package/brands/current/assets/glyphs/README.md

@@ -0,0 +1,29 @@
+# Glyphs — Lucide
+
+76 icons from [Lucide](https://lucide.dev) v0.469.0, **ISC licensed** (permissive:
+use, modify and redistribute, keep the notice). They replace the numbered PNGs
+that were reverse-extracted from a reference deck.
+
+Two problems they fix, both of which were standing known gaps:
+
+**Polarity.** The old glyphs were baked white or baked accent, so a white one on
+a light-theme `surface` tile was invisible. These are single-colour stroke SVGs
+with `stroke="currentColor"`, and the kit substitutes the theme's ink colour at
+build time. There is no variant to pick and nothing to get wrong.
+
+**Meaning.** They have names. A spec says `icon: "shield-check"`, not
+`icon: "icon-17.png"`. `index.json` groups them by what a deck actually needs —
+governance, workforce, platform, process, outcome, signal.
+
+## How they reach the deck
+
+As vector. pptxgenjs writes the OOXML `asvg:svgBlip` extension with a raster
+fallback, so PowerPoint 2016+ renders the SVG and anything older gets the PNG.
+Nothing is rasterised at build time, so the kit still needs no native
+dependency.
+
+## The old set
+
+`../icons/*.png` is still there and still works — every existing spec references
+those filenames. New specs should use glyph names. The two sets can coexist
+indefinitely; `iconTile` resolves a name first and falls back to a filename.

package/brands/current/assets/glyphs/activity.svg

@@ -0,0 +1,15 @@
+<!-- @license lucide-static v0.469.0 - ISC -->
+<svg
+  class="lucide lucide-activity"
+  xmlns="http://www.w3.org/2000/svg"
+  width="24"
+  height="24"
+  viewBox="0 0 24 24"
+  fill="none"
+  stroke="currentColor"
+  stroke-width="2"
+  stroke-linecap="round"
+  stroke-linejoin="round"
+>
+  <path d="M22 12h-2.48a2 2 0 0 0-1.93 1.46l-2.35 8.36a.25.25 0 0 1-.48 0L9.24 2.18a.25.25 0 0 0-.48 0l-2.35 8.36A2 2 0 0 1 4.49 12H2" />
+</svg>

package/brands/current/assets/glyphs/atom.svg

@@ -0,0 +1,17 @@
+<!-- @license lucide-static v0.469.0 - ISC -->
+<svg
+  class="lucide lucide-atom"
+  xmlns="http://www.w3.org/2000/svg"
+  width="24"
+  height="24"
+  viewBox="0 0 24 24"
+  fill="none"
+  stroke="currentColor"
+  stroke-width="2"
+  stroke-linecap="round"
+  stroke-linejoin="round"
+>
+  <circle cx="12" cy="12" r="1" />
+  <path d="M20.2 20.2c2.04-2.03.02-7.36-4.5-11.9-4.54-4.52-9.87-6.54-11.9-4.5-2.04 2.03-.02 7.36 4.5 11.9 4.54 4.52 9.87 6.54 11.9 4.5Z" />
+  <path d="M15.7 15.7c4.52-4.54 6.54-9.87 4.5-11.9-2.03-2.04-7.36-.02-11.9 4.5-4.52 4.54-6.54 9.87-4.5 11.9 2.03 2.04 7.36.02 11.9-4.5Z" />
+</svg>

package/brands/current/assets/glyphs/badge-check.svg

@@ -0,0 +1,16 @@
+<!-- @license lucide-static v0.469.0 - ISC -->
+<svg
+  class="lucide lucide-badge-check"
+  xmlns="http://www.w3.org/2000/svg"
+  width="24"
+  height="24"
+  viewBox="0 0 24 24"
+  fill="none"
+  stroke="currentColor"
+  stroke-width="2"
+  stroke-linecap="round"
+  stroke-linejoin="round"
+>
+  <path d="M3.85 8.62a4 4 0 0 1 4.78-4.77 4 4 0 0 1 6.74 0 4 4 0 0 1 4.78 4.78 4 4 0 0 1 0 6.74 4 4 0 0 1-4.77 4.78 4 4 0 0 1-6.75 0 4 4 0 0 1-4.78-4.77 4 4 0 0 1 0-6.76Z" />
+  <path d="m9 12 2 2 4-4" />
+</svg>

package/brands/current/assets/glyphs/bell.svg

@@ -0,0 +1,16 @@
+<!-- @license lucide-static v0.469.0 - ISC -->
+<svg
+  class="lucide lucide-bell"
+  xmlns="http://www.w3.org/2000/svg"
+  width="24"
+  height="24"
+  viewBox="0 0 24 24"
+  fill="none"
+  stroke="currentColor"
+  stroke-width="2"
+  stroke-linecap="round"
+  stroke-linejoin="round"
+>
+  <path d="M10.268 21a2 2 0 0 0 3.464 0" />
+  <path d="M3.262 15.326A1 1 0 0 0 4 17h16a1 1 0 0 0 .74-1.673C19.41 13.956 18 12.499 18 8A6 6 0 0 0 6 8c0 4.499-1.411 5.956-2.738 7.326" />
+</svg>

package/brands/current/assets/glyphs/blocks.svg

@@ -0,0 +1,16 @@
+<!-- @license lucide-static v0.469.0 - ISC -->
+<svg
+  class="lucide lucide-blocks"
+  xmlns="http://www.w3.org/2000/svg"
+  width="24"
+  height="24"
+  viewBox="0 0 24 24"
+  fill="none"
+  stroke="currentColor"
+  stroke-width="2"
+  stroke-linecap="round"
+  stroke-linejoin="round"
+>
+  <rect width="7" height="7" x="14" y="3" rx="1" />
+  <path d="M10 21V8a1 1 0 0 0-1-1H4a1 1 0 0 0-1 1v12a1 1 0 0 0 1 1h12a1 1 0 0 0 1-1v-5a1 1 0 0 0-1-1H3" />
+</svg>

package/brands/current/assets/glyphs/book-open.svg

@@ -0,0 +1,16 @@
+<!-- @license lucide-static v0.469.0 - ISC -->
+<svg
+  class="lucide lucide-book-open"
+  xmlns="http://www.w3.org/2000/svg"
+  width="24"
+  height="24"
+  viewBox="0 0 24 24"
+  fill="none"
+  stroke="currentColor"
+  stroke-width="2"
+  stroke-linecap="round"
+  stroke-linejoin="round"
+>
+  <path d="M12 7v14" />
+  <path d="M3 18a1 1 0 0 1-1-1V4a1 1 0 0 1 1-1h5a4 4 0 0 1 4 4 4 4 0 0 1 4-4h5a1 1 0 0 1 1 1v13a1 1 0 0 1-1 1h-6a3 3 0 0 0-3 3 3 3 0 0 0-3-3z" />
+</svg>

package/brands/current/assets/glyphs/bot.svg

@@ -0,0 +1,20 @@
+<!-- @license lucide-static v0.469.0 - ISC -->
+<svg
+  class="lucide lucide-bot"
+  xmlns="http://www.w3.org/2000/svg"
+  width="24"
+  height="24"
+  viewBox="0 0 24 24"
+  fill="none"
+  stroke="currentColor"
+  stroke-width="2"
+  stroke-linecap="round"
+  stroke-linejoin="round"
+>
+  <path d="M12 8V4H8" />
+  <rect width="16" height="12" x="4" y="8" rx="2" />
+  <path d="M2 14h2" />
+  <path d="M20 14h2" />
+  <path d="M15 13v2" />
+  <path d="M9 13v2" />
+</svg>

package/brands/current/assets/glyphs/boxes.svg

@@ -0,0 +1,26 @@
+<!-- @license lucide-static v0.469.0 - ISC -->
+<svg
+  class="lucide lucide-boxes"
+  xmlns="http://www.w3.org/2000/svg"
+  width="24"
+  height="24"
+  viewBox="0 0 24 24"
+  fill="none"
+  stroke="currentColor"
+  stroke-width="2"
+  stroke-linecap="round"
+  stroke-linejoin="round"
+>
+  <path d="M2.97 12.92A2 2 0 0 0 2 14.63v3.24a2 2 0 0 0 .97 1.71l3 1.8a2 2 0 0 0 2.06 0L12 19v-5.5l-5-3-4.03 2.42Z" />
+  <path d="m7 16.5-4.74-2.85" />
+  <path d="m7 16.5 5-3" />
+  <path d="M7 16.5v5.17" />
+  <path d="M12 13.5V19l3.97 2.38a2 2 0 0 0 2.06 0l3-1.8a2 2 0 0 0 .97-1.71v-3.24a2 2 0 0 0-.97-1.71L17 10.5l-5 3Z" />
+  <path d="m17 16.5-5-3" />
+  <path d="m17 16.5 4.74-2.85" />
+  <path d="M17 16.5v5.17" />
+  <path d="M7.97 4.42A2 2 0 0 0 7 6.13v4.37l5 3 5-3V6.13a2 2 0 0 0-.97-1.71l-3-1.8a2 2 0 0 0-2.06 0l-3 1.8Z" />
+  <path d="M12 8 7.26 5.15" />
+  <path d="m12 8 4.74-2.85" />
+  <path d="M12 13.5V8" />
+</svg>

package/brands/current/assets/glyphs/brain.svg

@@ -0,0 +1,23 @@
+<!-- @license lucide-static v0.469.0 - ISC -->
+<svg
+  class="lucide lucide-brain"
+  xmlns="http://www.w3.org/2000/svg"
+  width="24"
+  height="24"
+  viewBox="0 0 24 24"
+  fill="none"
+  stroke="currentColor"
+  stroke-width="2"
+  stroke-linecap="round"
+  stroke-linejoin="round"
+>
+  <path d="M12 5a3 3 0 1 0-5.997.125 4 4 0 0 0-2.526 5.77 4 4 0 0 0 .556 6.588A4 4 0 1 0 12 18Z" />
+  <path d="M12 5a3 3 0 1 1 5.997.125 4 4 0 0 1 2.526 5.77 4 4 0 0 1-.556 6.588A4 4 0 1 1 12 18Z" />
+  <path d="M15 13a4.5 4.5 0 0 1-3-4 4.5 4.5 0 0 1-3 4" />
+  <path d="M17.599 6.5a3 3 0 0 0 .399-1.375" />
+  <path d="M6.003 5.125A3 3 0 0 0 6.401 6.5" />
+  <path d="M3.477 10.896a4 4 0 0 1 .585-.396" />
+  <path d="M19.938 10.5a4 4 0 0 1 .585.396" />
+  <path d="M6 18a4 4 0 0 1-1.967-.516" />
+  <path d="M19.967 17.484A4 4 0 0 1 18 18" />
+</svg>

package/brands/current/assets/glyphs/briefcase.svg

@@ -0,0 +1,16 @@
+<!-- @license lucide-static v0.469.0 - ISC -->
+<svg
+  class="lucide lucide-briefcase"
+  xmlns="http://www.w3.org/2000/svg"
+  width="24"
+  height="24"
+  viewBox="0 0 24 24"
+  fill="none"
+  stroke="currentColor"
+  stroke-width="2"
+  stroke-linecap="round"
+  stroke-linejoin="round"
+>
+  <path d="M16 20V4a2 2 0 0 0-2-2h-4a2 2 0 0 0-2 2v16" />
+  <rect width="20" height="14" x="2" y="6" rx="2" />
+</svg>

package/brands/current/assets/glyphs/building-2.svg

@@ -0,0 +1,21 @@
+<!-- @license lucide-static v0.469.0 - ISC -->
+<svg
+  class="lucide lucide-building-2"
+  xmlns="http://www.w3.org/2000/svg"
+  width="24"
+  height="24"
+  viewBox="0 0 24 24"
+  fill="none"
+  stroke="currentColor"
+  stroke-width="2"
+  stroke-linecap="round"
+  stroke-linejoin="round"
+>
+  <path d="M6 22V4a2 2 0 0 1 2-2h8a2 2 0 0 1 2 2v18Z" />
+  <path d="M6 12H4a2 2 0 0 0-2 2v6a2 2 0 0 0 2 2h2" />
+  <path d="M18 9h2a2 2 0 0 1 2 2v9a2 2 0 0 1-2 2h-2" />
+  <path d="M10 6h4" />
+  <path d="M10 10h4" />
+  <path d="M10 14h4" />
+  <path d="M10 18h4" />
+</svg>