arkaos 4.29.0 → 4.30.0

package/departments/brand/skills/design-system/references/design-md-spec.md

@@ -0,0 +1,454 @@
+# design.md — portable design-system spec + exports
+
+> Source: merge of `references/design-md.md` + `references/export-formats.md` from the **hallmark** skill repo (MIT — see `hallmark.LICENSE` in this references directory). Adapted for ArkaOS; an ArkaOS bridge paragraph closes the file.
+
+`design.md` is the opt-in portable design system: loaded ONLY when the user explicitly asks to lock the current build's design system into a portable file. The default build flow does NOT auto-emit `design.md`. The user iterates freely until they say the system is settled, then asks for it.
+
+This spec is **also** used by [`design-dna-study.md`](design-dna-study.md) when the user — after a successful `study` diagnosis — asks for the DNA to be emitted as a portable system. The format below is shared between the two paths; the only differences are spelled out in § Two emission paths (default vs study) and in [`design-dna-study.md`](design-dna-study.md) § Emitting a `design.md` from `study`.
+
+## Triggers (phrase-only — no new verb)
+
+Fire ONLY when the user says one of:
+
+- *"lock the system"* / *"lock the design system"* / *"lock the DNA"* / *"lock this DNA"*
+- *"give me a design.md"* / *"write a design.md"* / *"export this as a design.md"*
+- *"extract this to a design system"* / *"extract the tokens"* / *"extract the DNA"*
+- *"make this portable"* / *"make the DNA portable"*
+- *"I want to use this in another project"*
+
+For everything else — including the default build, a redesign of a single page, and free iteration on the same brief — skip. Single-page work stays token-portable via `tokens.css`; `design.md` is the explicit lock-in step.
+
+## Two emission paths (default vs study)
+
+The same `design.md` format is emitted from two different entry points. They differ in which signals seed the file and in how strict the refusal layer is.
+
+| | **Default-build path** (lock the system) | **Study path** (lock the DNA) |
+| --- | --- | --- |
+| **Trigger context** | After at least one build the user has iterated on and is satisfied with | After a successful `study` diagnosis (image or URL) |
+| **Source of tokens** | The build's in-memory token state | The studied DNA — exact from CSS in URL mode, estimated from bands in image mode |
+| **Refusal layer** | None — the user owns the build they iterated on | Tighter — see [`design-dna-study.md`](design-dna-study.md) § Emission-refusal layer. URL mode requires attestation; third-party URLs are refused |
+| **`## Provenance` block** | Omitted (the system is the user's own work) | Required — records source mode, URL or "image", date, attestation answer, confidence note |
+| **`## Notes` block** | Optional — covers any decisions worth remembering | Required — carries the diagnosis's "anti-patterns to NOT carry over" list |
+
+Both paths produce a `design.md` that subsequent runs can read; the file format is uniform once written.
+
+## Scope
+
+- **Page-builds only.** Skip on component-scope — a single component is too small to be a system.
+- **Multi-page redesign keeps existing behaviour.** A multi-page redesign produces the heavyweight `design.md` as part of its own flow (upstream: `verbs/redesign.md` § Multi-page flow — unported). That flow already implies a locked system, so the rule there is unchanged.
+- **No-overwrite policy.** If `design.md` already exists at the project root, do NOT overwrite. Refresh its `## Exports` section instead and emit one line: *"design.md detected — refreshed Exports, system unchanged."*
+
+## CTA — surface the offer in the build preview
+
+After every default + redesign page-build, append one quiet line at the bottom of the preview block:
+
+> *System portable? Say `lock the system` to extract this build's tokens + voice into a `design.md`.*
+
+Skip the CTA when (a) the build is component-scope, or (b) `design.md` already exists in the project (system is already locked).
+
+## Format (the tight version)
+
+Write the file at the project root. Match the project's case convention (`design.md` or `DESIGN.md`). Target ~45 lines — enough to seed a real app, not so much that it becomes a wiki to maintain. The format:
+
+````markdown
+# Design — <Project name>
+
+Locked design system. Future runs read this file first; pages defer
+to it. Amend intentionally — the file is the rule.
+
+## System
+- Genre · <editorial / modern-minimal / atmospheric / playful>
+- Macrostructure · <name>
+- Theme · <catalog: NAME · or · custom (vibe: "<4–8 words>")>
+- Axes · <paper-band> / <display-style> / <accent-hue>
+
+## Tokens (canonical · `tokens.css` is the source of truth)
+```css
+:root {
+  --color-paper:      oklch(<L> <C> <H>);
+  --color-paper-2:    oklch(<L> <C> <H>);
+  --color-ink:        oklch(<L> <C> <H>);
+  --color-ink-2:      oklch(<L> <C> <H>);
+  --color-rule:       oklch(<L> <C> <H>);
+  --color-accent:     oklch(<L> <C> <H>);
+  --color-accent-ink: oklch(<L> <C> <H>);
+  --color-focus:      oklch(<L> <C> <H>);
+
+  --font-display: "<face>", ...;
+  --font-body:    "<face>", ...;
+  --font-mono:    "<face>", ...;
+
+  /* 4-pt spacing scale, named: --space-3xs … --space-4xl. See tokens.css.   */
+  /* Type scale, 1.25 (major-third) ratio: --text-xs … --text-display.       */
+
+  --ease-out: cubic-bezier(0.16, 1, 0.3, 1);
+  --dur-fast: 180ms;  --dur-base: 240ms;  --dur-slow: 320ms;
+
+  --radius-card: <px>;  --radius-pill: <px>;  --radius-input: <px>;
+}
+```
+
+## CTA voice
+- Primary · <fill colour> · <radius> · <padding rhythm>
+- Secondary · <outline / ghost> · <same radius>
+
+## Motion stance
+- <silent · 1–2 reveal primitives · motion-cut>
+- Reduced-motion fallback · ≤150 ms opacity crossfade.
+
+## Exports
+`tokens.css` (in this project) is the source of truth. For Tailwind v4
+`@theme`, DTCG `tokens.json`, or shadcn/ui CSS variables, ask *"extend
+design.md with Tailwind exports"* (or the format you want) — they will
+be appended per § Export formats below.
+````
+
+State the picks aloud BEFORE writing the file. *"Genre: editorial. Macrostructure: Long Document. Theme: catalog Editorial. Locking this as the project's system."* Then write.
+
+## After the file is written
+
+Once `design.md` exists, the pre-flight scan detects it on every subsequent run. From that point on:
+
+- All future runs READ `design.md` first; subsequent picks (genre / theme / typography / motion / CTA voice) defer to it.
+- The diversification rule INVERTS — pages must SHARE the system, not differ from each other.
+- If a future page genuinely needs a different system, AMEND `design.md` with a `## Variants` section rather than overriding locally — the file evolves; per-page overrides do not.
+
+## Why opt-in (not auto-emit)
+
+Briefs iterate. The first build is rarely the settled design. Auto-emitting `design.md` on every default build would either churn the file across iterations or lock a weak system before the user has reviewed it. Opt-in mirrors how design teams actually work — formalise the system after the patterns hold, not on day one. The CTA in the preview block keeps the feature discoverable without forcing it.
+
+---
+
+# Export formats
+
+Loaded when emitting the design system as portable tokens. Defines the four canonical formats every emission writes:
+
+1. **`tokens.css`** — the source of truth. Always emitted alongside the page CSS.
+2. **Tailwind v4 `@theme`** — for projects on Tailwind. Emitted into `design.md`'s Exports section on multi-page projects.
+3. **DTCG `tokens.json`** — for projects using a token pipeline (Style Dictionary, Token Studio, Cobalt). Emitted into `design.md`.
+4. **shadcn/ui CSS variables** — for projects using shadcn/ui's component library. Emitted into `design.md`.
+
+The output rule: `tokens.css` is always written. The other three live inline in `design.md` so the user copies whichever they need into a new project. **No new verb.** This is a side effect of every build.
+
+---
+
+## Token taxonomy — the source of truth
+
+Every build writes these tokens (or a subset, if the page doesn't use one). The names are the source; every other format is a translation.
+
+| Token | Type | Example value |
+| --- | --- | --- |
+| `--color-paper` | colour | `oklch(96% 0.018 80)` |
+| `--color-paper-2` | colour | `oklch(94% 0.020 80)` |
+| `--color-paper-3` | colour | `oklch(91% 0.022 80)` |
+| `--color-ink` | colour | `oklch(15% 0.012 80)` |
+| `--color-ink-2` | colour | `oklch(28% 0.014 80)` |
+| `--color-rule` | colour | `oklch(86% 0.018 80)` |
+| `--color-rule-2` | colour | `oklch(72% 0.020 80)` |
+| `--color-muted` | colour | `oklch(50% 0.014 80)` |
+| `--color-neutral` | colour | `oklch(38% 0.012 80)` |
+| `--color-accent` | colour | `oklch(58% 0.16 70)` |
+| `--color-accent-ink` | colour | (text on accent fill, ≥ APCA 7:1) |
+| `--color-focus` | colour | (often = accent at higher chroma) |
+| `--font-display` | font | `"Fraunces", ui-serif, Georgia, serif` |
+| `--font-body` | font | `"Geist", ui-sans-serif, system-ui, sans-serif` |
+| `--font-outlier` | font | `"Geist Mono", ui-monospace, monospace` |
+| `--space-3xs` … `--space-5xl` | length | 4-pt scale: `0.25rem` … `8rem` |
+| `--text-xs` … `--text-display` | length | 1.25 (major-third) ratio scale |
+| `--ease-out` / `--ease-in` / `--ease-in-out` | easing | `cubic-bezier(0.16, 1, 0.3, 1)` etc. |
+| `--dur-micro` / `--dur-short` / `--dur-long` | time | `120ms` / `220ms` / `420ms` |
+| `--rule-hair` / `--rule-fine` | length | `1px` / `2px` |
+| `--radius-card` / `--radius-pill` / `--radius-input` | length | varies per theme |
+| `--shadow-card` | shadow | varies per theme |
+
+If the page introduces *additional* tokens, name them by role and add to `tokens.css`. Don't make up token names downstream that aren't in `tokens.css` — the source of truth is the source of truth.
+
+---
+
+## Format 1 — `tokens.css`
+
+The source. Plain CSS custom properties at `:root`. Every page CSS imports this file at the top:
+
+```css
+@import "tokens.css";
+/* page CSS continues — uses var(--color-paper), never raw values */
+```
+
+Or, if the project uses a CSS bundler / framework that doesn't honour bare `@import`, the project's existing entry-point imports `tokens.css` before the page CSS that consumes it (keep it among the other top-of-file `@import`s, never above or in place of `@import "tailwindcss"`). The page CSS still references tokens by name, never by raw value.
+
+**Worked example — editorial theme (Specimen-like):**
+
+```css
+:root {
+  --color-paper:        oklch(96% 0.018 80);
+  --color-paper-2:      oklch(94% 0.020 80);
+  --color-paper-3:      oklch(91% 0.022 80);
+  --color-rule:         oklch(86% 0.020 78);
+  --color-rule-2:       oklch(72% 0.022 78);
+  --color-muted:        oklch(50% 0.018 78);
+  --color-neutral:      oklch(38% 0.014 76);
+  --color-ink-2:        oklch(28% 0.012 75);
+  --color-ink:          oklch(15% 0.010 75);
+  --color-accent:       oklch(58% 0.16 60);
+  --color-accent-ink:   oklch(98% 0.012 75);
+  --color-focus:        oklch(58% 0.16 60);
+
+  --font-display: "Fraunces", "Cardo", ui-serif, Georgia, serif;
+  --font-body:    "Geist", "Söhne", ui-sans-serif, system-ui, sans-serif;
+  --font-outlier: "Geist Mono", "JetBrains Mono", ui-monospace, monospace;
+
+  --display-weight: 400;
+  --display-style:  italic;
+  --tracking-display: -0.02em;
+  --tracking-label:   0.10em;
+
+  --text-xs:      0.75rem;
+  --text-sm:      0.875rem;
+  --text-md:      1.125rem;
+  --text-lg:      1.375rem;
+  --text-xl:      1.75rem;
+  --text-2xl:     2.25rem;
+  --text-display: clamp(3rem, 6vw + 1rem, 6.5rem);
+
+  --space-3xs: 0.25rem;
+  --space-2xs: 0.5rem;
+  --space-xs:  0.75rem;
+  --space-sm:  1rem;
+  --space-md:  1.5rem;
+  --space-lg:  2rem;
+  --space-xl:  3rem;
+  --space-2xl: 4.5rem;
+  --space-3xl: 7rem;
+  --space-4xl: 11rem;
+
+  --rule-hair: 0.5px;
+  --rule-fine: 1px;
+  --radius-card:  0;
+  --radius-pill:  0;
+  --radius-input: 0;
+
+  --ease-out:    cubic-bezier(0.16, 1, 0.3, 1);
+  --ease-in:     cubic-bezier(0.7, 0, 0.84, 0);
+  --ease-in-out: cubic-bezier(0.65, 0, 0.35, 1);
+
+  --dur-micro: 120ms;
+  --dur-short: 220ms;
+  --dur-long:  420ms;
+}
+```
+
+**Worked example — modern-minimal theme (austere, pure-white):**
+
+```css
+:root {
+  --color-paper:      oklch(100%  0     0);
+  --color-paper-2:    oklch(98.5% 0     0);
+  --color-paper-3:    oklch(96%   0     0);
+  --color-rule:       oklch(91%   0     0);
+  --color-rule-2:     oklch(82%   0     0);
+  --color-muted:      oklch(55%   0     0);
+  --color-neutral:    oklch(40%   0     0);
+  --color-ink-2:      oklch(28%   0     0);
+  --color-ink:        oklch(15%   0     0);
+  --color-accent:     oklch(15%   0     0);
+  --color-accent-ink: oklch(100%  0     0);
+  --color-focus:      oklch(60%   0.10  240);
+
+  --font-display: "Geist", "Inter", ui-sans-serif, system-ui, sans-serif;
+  --font-body:    "Geist", "Inter", ui-sans-serif, system-ui, sans-serif;
+  --font-outlier: "Geist Mono", ui-monospace, "SF Mono", Menlo, monospace;
+
+  --display-weight: 600;
+  --display-style:  normal;
+  --tracking-display: -0.025em;
+
+  --radius-card:  8px;
+  --radius-pill:  999px;
+  --radius-input: 8px;
+}
+```
+
+---
+
+## Format 2 — Tailwind v4 `@theme`
+
+Tailwind v4 reads CSS variables inside `@theme` and generates utilities (`bg-paper`, `text-ink`, etc.) automatically. The translation from the canonical tokens is direct — same variable names, same OKLCH values:
+
+```css
+@theme {
+  /* Colours */
+  --color-paper:        oklch(96% 0.018 80);
+  --color-paper-2:      oklch(94% 0.020 80);
+  --color-paper-3:      oklch(91% 0.022 80);
+  --color-rule:         oklch(86% 0.020 78);
+  --color-rule-2:       oklch(72% 0.022 78);
+  --color-muted:        oklch(50% 0.018 78);
+  --color-neutral:      oklch(38% 0.014 76);
+  --color-ink-2:        oklch(28% 0.012 75);
+  --color-ink:          oklch(15% 0.010 75);
+  --color-accent:       oklch(58% 0.16 60);
+  --color-focus:        oklch(58% 0.16 60);
+
+  /* Fonts */
+  --font-display: "Fraunces", "Cardo", ui-serif, Georgia, serif;
+  --font-body:    "Geist", ui-sans-serif, system-ui, sans-serif;
+  --font-outlier: "Geist Mono", ui-monospace, monospace;
+
+  /* Spacing — Tailwind reads --spacing-* by default; we keep the --space-* names alongside */
+  --spacing-3xs: 0.25rem;
+  --spacing-2xs: 0.5rem;
+  --spacing-xs:  0.75rem;
+  --spacing-sm:  1rem;
+  --spacing-md:  1.5rem;
+  --spacing-lg:  2rem;
+  --spacing-xl:  3rem;
+  --spacing-2xl: 4.5rem;
+
+  /* Type scale — Tailwind reads --text-* */
+  --text-xs:      0.75rem;
+  --text-sm:      0.875rem;
+  --text-md:      1.125rem;
+  --text-lg:      1.375rem;
+  --text-xl:      1.75rem;
+  --text-2xl:     2.25rem;
+
+  /* Radius */
+  --radius-card:  0;
+  --radius-pill:  0;
+  --radius-input: 0;
+
+  /* Easings — Tailwind reads --ease-* */
+  --ease-out:    cubic-bezier(0.16, 1, 0.3, 1);
+  --ease-in:     cubic-bezier(0.7, 0, 0.84, 0);
+  --ease-in-out: cubic-bezier(0.65, 0, 0.35, 1);
+}
+```
+
+Notes:
+- Tailwind v4 expects `--spacing-*` (with `ing`) for the spacing utilities. We mirror `--space-*` to `--spacing-*` so both names work.
+- `--text-*` works as-is (Tailwind v4 picks them up for `text-md` etc.).
+- `--font-*` becomes `font-display` / `font-body` / `font-outlier` utilities.
+- The user's `tailwind.config.{ts,js}` may need `@source` directives but no `theme.extend` — v4 reads `@theme` directly.
+
+---
+
+## Format 3 — DTCG `tokens.json`
+
+W3C Design Tokens Community Group format. For projects using Style Dictionary, Cobalt, or Token Studio. Path-based; OKLCH stays as a string value; `$type` is required.
+
+```json
+{
+  "$schema": "https://design-tokens.github.io/community-group/format/",
+  "color": {
+    "paper":   { "$value": "oklch(96% 0.018 80)", "$type": "color" },
+    "paper-2": { "$value": "oklch(94% 0.020 80)", "$type": "color" },
+    "paper-3": { "$value": "oklch(91% 0.022 80)", "$type": "color" },
+    "rule":    { "$value": "oklch(86% 0.020 78)", "$type": "color" },
+    "rule-2":  { "$value": "oklch(72% 0.022 78)", "$type": "color" },
+    "muted":   { "$value": "oklch(50% 0.018 78)", "$type": "color" },
+    "neutral": { "$value": "oklch(38% 0.014 76)", "$type": "color" },
+    "ink-2":   { "$value": "oklch(28% 0.012 75)", "$type": "color" },
+    "ink":     { "$value": "oklch(15% 0.010 75)", "$type": "color" },
+    "accent":  { "$value": "oklch(58% 0.16 60)",  "$type": "color" },
+    "focus":   { "$value": "oklch(58% 0.16 60)",  "$type": "color" }
+  },
+  "font": {
+    "display": { "$value": "Fraunces, Cardo, ui-serif, Georgia, serif", "$type": "fontFamily" },
+    "body":    { "$value": "Geist, ui-sans-serif, system-ui, sans-serif", "$type": "fontFamily" },
+    "outlier": { "$value": "Geist Mono, ui-monospace, monospace",         "$type": "fontFamily" }
+  },
+  "size": {
+    "text-xs":      { "$value": "0.75rem",  "$type": "dimension" },
+    "text-sm":      { "$value": "0.875rem", "$type": "dimension" },
+    "text-md":      { "$value": "1.125rem", "$type": "dimension" },
+    "text-lg":      { "$value": "1.375rem", "$type": "dimension" },
+    "text-xl":      { "$value": "1.75rem",  "$type": "dimension" },
+    "text-2xl":     { "$value": "2.25rem",  "$type": "dimension" },
+    "text-display": { "$value": "6rem",     "$type": "dimension" }
+  },
+  "space": {
+    "3xs": { "$value": "0.25rem", "$type": "dimension" },
+    "2xs": { "$value": "0.5rem",  "$type": "dimension" },
+    "xs":  { "$value": "0.75rem", "$type": "dimension" },
+    "sm":  { "$value": "1rem",    "$type": "dimension" },
+    "md":  { "$value": "1.5rem",  "$type": "dimension" },
+    "lg":  { "$value": "2rem",    "$type": "dimension" },
+    "xl":  { "$value": "3rem",    "$type": "dimension" },
+    "2xl": { "$value": "4.5rem",  "$type": "dimension" },
+    "3xl": { "$value": "7rem",    "$type": "dimension" },
+    "4xl": { "$value": "11rem",   "$type": "dimension" }
+  },
+  "duration": {
+    "micro": { "$value": "120ms", "$type": "duration" },
+    "short": { "$value": "220ms", "$type": "duration" },
+    "long":  { "$value": "420ms", "$type": "duration" }
+  }
+}
+```
+
+Notes:
+- DTCG accepts `oklch(...)` strings on modern tooling. If the user's pipeline doesn't, convert to hex (lossy — flag this) or to `color(oklch ...)` (CSS Color 4).
+- The `text-display` value uses a fixed `6rem` for portability — the responsive `clamp(...)` belongs in CSS, not in token JSON.
+
+---
+
+## Format 4 — shadcn/ui CSS variables
+
+shadcn/ui's component library reads CSS custom properties with specific names, in a specific shape. The values are **space-separated** triples (no `oklch()` wrapper, no commas) so shadcn can compose them with `oklch(<value> / <alpha>)`.
+
+The translation from the canonical tokens:
+
+```css
+:root {
+  --background:           96%   0.018 80;     /* paper */
+  --foreground:           15%   0.010 75;     /* ink */
+
+  --card:                 94%   0.020 80;     /* paper-2 */
+  --card-foreground:      15%   0.010 75;     /* ink */
+
+  --popover:              94%   0.020 80;     /* paper-2 */
+  --popover-foreground:   15%   0.010 75;     /* ink */
+
+  --primary:              58%   0.16  60;     /* accent */
+  --primary-foreground:   98%   0.012 75;     /* accent-ink */
+
+  --secondary:            91%   0.022 80;     /* paper-3 */
+  --secondary-foreground: 28%   0.012 75;     /* ink-2 */
+
+  --muted:                86%   0.020 78;     /* rule */
+  --muted-foreground:     50%   0.018 78;     /* muted */
+
+  --accent:               58%   0.16  60;     /* accent (same as primary in this taxonomy) */
+  --accent-foreground:    98%   0.012 75;
+
+  --destructive:          58%   0.20  25;     /* warm red, fixed */
+  --destructive-foreground: 98% 0.012 75;
+
+  --border:               86%   0.020 78;     /* rule */
+  --input:                86%   0.020 78;     /* rule */
+  --ring:                 58%   0.16  60;     /* focus */
+
+  --radius:               0;                   /* radius-card; shadcn uses one value */
+}
+```
+
+Then the user's `tailwind.config.ts` (or v4 `@theme`) reads them with `oklch(var(--background))`. The accent → shadcn's primary is the canonical mapping; secondary → paper-3.
+
+If the user wants a dark variant, mirror with dark theme tokens under a `.dark` selector (a dark catalog theme — e.g. [lumen Night Foundry](themes/lumen.md) — supplies the values).
+
+---
+
+## Output rule
+
+When emitting exports:
+
+1. **Always** write `tokens.css` next to the page CSS (or in the project root for multi-file projects). Format 1.
+2. **On `design.md`-managed projects** (multi-page), embed all four formats inline in `design.md`'s Exports section. The user copies whichever they need.
+3. **On Tailwind projects** (detected at pre-flight), additionally surface the Tailwind `@theme` block in the build output so the user knows where to paste it (typically into `app/globals.css` or the equivalent).
+4. **Merge into an existing entry stylesheet; never overwrite it.** When the target project already has `app/globals.css` (or `src/index.css`, `src/styles/global.css`): keep its existing `@import "tailwindcss"` / `@tailwind base|components|utilities` directives exactly as they are, append the `:root` tokens and base rules *after* them, and keep any `@import "tokens.css"` at the very top of the file (CSS parses `@import` only before other rules, so a misplaced one is silently dropped and your tokens vanish). If the project already defines brand tokens (`--background`, `--foreground`, a Tailwind `@theme`), map the roles onto those names rather than adding a parallel set, or scope the tokens under a wrapper class. Replace the file outright only when the user has asked for a full takeover.
+
+Don't blanket-emit tokens.json or shadcn variables on single-page projects — the user can copy them out of `design.md` if they upgrade to a multi-page system.
+
+---
+
+ArkaOS bridge: when a project declares `design-system.yaml` (rule `design-system-locked`), mirror the emitted tokens into the token source named by the `[arka:design] tokens=` marker field; the per-project linter (`core.governance.design_system_lint`) stays advisory. The emitted file lives at the project root as `design.md`.

package/departments/brand/skills/design-system/references/hallmark.LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Hallmark contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/departments/brand/skills/design-system/references/impeccable.LICENSE

@@ -0,0 +1,191 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to the Licensor for inclusion in the Work by the copyright
+      owner or by an individual or Legal Entity authorized to submit on
+      behalf of the copyright owner. For the purposes of this definition,
+      "submitted" means any form of electronic, verbal, or written
+      communication sent to the Licensor or its representatives, including
+      but not limited to communication on electronic mailing lists, source
+      code control systems, and issue tracking systems that are managed by,
+      or on behalf of, the Licensor for the purpose of discussing and
+      improving the Work, but excluding communication that is conspicuously
+      marked or otherwise designated in writing by the copyright owner as
+      "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2025 Paul Bakaus
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.