@payfit/unity-themes 2.68.15 → 2.68.17

package/dist/esm/index.js

@@ -2,5 +2,4 @@ import { twMergeConfig as e } from "./utils/merge-config.js";
 import { classNames as t, clsx as n, cn as r } from "./utils/cn.js";
 import { uyMerge as i } from "./utils/tailwind-merge.js";
 import { uyTv as a } from "./utils/tailwind-variants.js";
-import { UnityThemeProvider as o, useUnityTheme as s } from "./components/unity-theme-provider.js";
-export { o as UnityThemeProvider, t as classNames, n as clsx, r as cn, e as twMergeConfig, s as useUnityTheme, i as uyMerge, a as uyTv };
+export { t as classNames, n as clsx, r as cn, e as twMergeConfig, i as uyMerge, a as uyTv };

package/dist/esm/scripts/actions/compose-multi-theme.d.ts

@@ -1,8 +1,8 @@
 export interface ComposeInput {
-    /** css/variables output for legacy (:root selector) */
-    legacyCss: string;
-    /** css/variables output for rebrand ([data-uy-theme="rebrand"] selector) */
-    rebrandCss: string;
+    /** css/variables output for the default theme (:root selector) */
+    defaultCss: string;
+    /** css/variables output for the compact theme ([data-unity-theme="compact"]) */
+    compactCss: string;
     /** css/unity-theme output (@theme block + grid/typography utilities) */
     themeCss: string;
     /** File header + imports */

package/dist/esm/scripts/style-dictionary-config.d.ts

@@ -9,6 +9,6 @@ export declare const sharedLogConfig: {
 };
 export declare const createThemeStyleDictionary: ({ projectRoot, theme, }: {
     projectRoot: string;
-    theme: "legacy" | "rebrand";
+    theme: "default" | "compact";
 }) => StyleDictionary;
 export default StyleDictionary;

package/dist/esm/types.d.ts

@@ -0,0 +1,2 @@
+/** Themes supported by the generated Unity assets and CSS. */
+export type UnityTheme = 'default' | 'compact';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@payfit/unity-themes",
-  "version": "2.68.15",
+  "version": "2.68.17",
   "main": "./dist/esm/index.js",
   "types": "./dist/esm/index.d.ts",
   "style": "./dist/css/unity.css",
@@ -52,8 +52,7 @@
     "@storybook/addon-a11y": "10.6.0",
     "@storybook/addon-docs": "10.6.0",
     "@storybook/addon-links": "10.6.0",
-    "@storybook/addon-mcp": "0.7.0",
-    "@storybook/addon-themes": "10.6.0",
+    "@storybook/addon-mcp": "10.6.0",
     "@storybook/addon-vitest": "10.6.0",
     "@storybook/react-vite": "10.6.0",
     "@tailwindcss/vite": "4.3.3",

package/skills/unity-themes/SKILL.md

@@ -22,7 +22,7 @@ Before implementation, perform a targeted search of
 `tokens-catalog.json` using `rg`, `jq`, or another file-reading command.
 Loading this skill alone does not count as consulting the catalog.
 
-1. Read [src/agent-references/tokens-catalog.json](../../src/agent-references/tokens-catalog.json) for exact catalog names, CSS variables, token families, resolved legacy/rebrand values, and references.
+1. Read [src/agent-references/tokens-catalog.json](../../src/agent-references/tokens-catalog.json) for exact catalog names, CSS variables, token families, resolved default values, and references.
 2. If the match is ambiguous or the raw definition is needed, inspect the DTCG files under `tokens/`.
 3. For utility-class syntax and common blueprints, inspect the generated projections under `src/storybook-mcp/` (for example `semantic-surface-colors.mdx`). These files are optimized guides, not the canonical token index.
 
@@ -38,7 +38,7 @@ jq '.tokens[] | select(.name | test("border-neutral"; "i"))' \
 1. Classify the request as a token name, CSS variable, generated class, resolved value, or design-intent question.
 2. Search the entire catalog and compare exact semantic matches before considering primitives.
 3. Use the catalog's `name` and `cssVariable`; do not reconstruct names from the DTCG path when a transform may have changed them.
-4. Preserve token references. Inspect `values.legacy` and `values.rebrand` to understand theme-specific resolution, and inspect `references` when explaining an alias.
+4. Preserve token references. Inspect `values.default` to understand the current theme resolution, and inspect `references` when explaining an alias.
 5. For classes, use the generated `src/storybook-mcp` blueprint for the relevant family and substitute only a catalog-confirmed token name. Do not enumerate or invent the complete class space.
 6. Prefer semantic tokens for product UI. Use primitives only when the intent has no semantic equivalent or the user explicitly asks for a raw palette value.
 7. Keep the `uy:` prefix on every Unity utility class.