astralkit 0.6.0 → 0.8.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,87 +1,109 @@
1
- # Changelog
2
-
3
- All notable changes to the `astralkit` SDK package.
4
-
5
- The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
6
- and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
-
8
- ## [0.6.0] — 2026-07-06
9
-
10
- ### Added
11
- - **`astralkit/theme-context` export** `AkThemeProvider` / `useAkTheme`, the React context that propagates per-component dark mode across Radix portal boundaries (Dialog/DropdownMenu/Popover content portals to `document.body`, escaping the `data-ak-dark-*` attribute scope). Installable components now import this from the SDK instead of shipping a local provider file. Adds `react >= 18` as an **optional** peer dependency — CSS-only consumers are unaffected.
12
- - **Sidebar theming layer** (authored post-0.5.0, first published here): `primitives/sidebar.css`, `ak-dark-material` / `ak-mirror-shimmer` and `ak-sidebar-*` utilities, plus the gradient / selection / inverse / surface-container token extensions the themed sidebar set depends on.
13
-
14
- ## [0.5.0] — 2026-06-12
15
-
16
- ### Added (Material 3 role grammar)
17
- - **45 new color-role tokens across both the v4 `@theme` and the v3 Tailwind plugin** (full v3/v4 parity). These complete the M3 role grammar that a large set of components now depend on:
18
- - **Surface containers** — `surface-3`, `surface-4`, `surface-container`, `surface-container-low`/`-lowest`/`-high`/`-highest`.
19
- - **Inverse** — `inverse-surface`, `inverse-on-surface` (dark cards on light themes and vice-versa).
20
- - **Secondary / tertiary / accent / error roles** — `secondary`(+`-container`), `on-secondary`(+`-container`), `tertiary`(+`-container`), `on-tertiary`(+`-container`), `accent`, `accent-soft`, `on-accent`, `error`, `error-container`, `on-error`, `on-error-container`, plus `primary-container`/`on-primary-container`.
21
- - **Surface / outline** — `on-surface`, `on-surface-variant`, `outline`, `outline-variant`, `scrim`.
22
- - **Per-theme controls** — `slider-fill`, `slider-ring` (themed Radix slider fill/ring).
23
- - **Status badges** `status-{new,beta,stable,deprecated}-{bg,border,text}`.
24
-
25
- ### Fixed
26
- - **`ak-skeleton` shimmer now respects `prefers-reduced-motion`.** Added a `@media (prefers-reduced-motion: reduce)` guard that stops the looping shimmer on `.ak-skeleton::after`.
27
-
28
- ## [0.4.0] 2026-06-06
29
-
30
- ### Added
31
- - **`astralkit/motion`** — accessible Framer Motion presets tuned to the AstralKit motion tokens (`fadeInUp`, `fadeIn`, `scaleIn`, `staggerContainer`/`staggerItem`, `revealOnScroll`, `hoverLift`/`pressable`, `akTransition`, and `withReducedMotion`). Plain variant/transition objects — importing adds **no dependency**; bring your own `motion` (MIT). All presets are `prefers-reduced-motion`-safe via `withReducedMotion`.
32
-
33
- ### Changed
34
- - **Motion policy reversed: Framer Motion is now allowed.** The previous "no Framer Motion" rule was based on a licensing misunderstanding — the `motion` package is MIT. `ai-rules.md` now permits Framer Motion + CSS + Lenis and points to the `astralkit/motion` presets; **GSAP** is the disallowed one (its license restricts sold products/templates).
35
- - `ai-rules.md`: motion guidance updated accordingly; premium-effect toolkit (`ak-card-glow`, `ak-mesh-*`, `ak-float`, `ak-scroll-fade`, etc.) emphasized for richer output.
36
-
37
- ## [0.3.8] — 2026-06-06
38
-
39
- ### Fixed
40
- - **Body font corrected to Inter.** `--font-ak-sans` was `'DM Sans'` in `astralkit-theme.css`, `astralkit-theme-v4.css`, and the Tailwind plugin, contradicting the canonical Inter body font. Replaced with `'Inter'` everywhere.
41
- - **Tailwind v3 plugin export repointed to `tailwind.cjs`.** `astralkit/tailwind` resolved to a stale `tailwind.js` that was both an incomplete token subset and broken under the package's `"type": "module"` (it used CommonJS `require()`). Removed `tailwind.js`; `astralkit/tailwind` now resolves to the complete `tailwind.cjs`. Single source of truth for v3 utilities.
42
-
43
- ### Added (v3 plugin token parity with v4)
44
- - Registered every token the v4 `@theme` auto-generates but the v3 plugin was missing: colors (`surface-raised`/`-soft`, `surface-glass`/`-strong`, `highlight-soft`/`-strong`, `skeleton-base`/`-shine`, `sheet-handle`, `pink`/`pink-subtle`), avatar/badge text sizes, spacing `ak-9`/`ak-11`/`ak-14`, `rounded-ak-xs`, `duration-ak-skeleton`, and `size-ak-avatar-xs`. v3 and v4 now expose an identical utility surface.
45
-
46
- ## [0.3.3] — 2026-04-22
47
-
48
- ### Changed
49
- - Widened `tailwind-merge` dependency range from `^2.2.0` to `^2.2.0 || ^3.0.0`. Tailwind CSS v4 projects use `tailwind-merge@v3` (which adds v4 class-name recognition), so accepting either major version lets npm dedupe to the host project's copy instead of nesting a second `node_modules/astralkit/node_modules/tailwind-merge`. Same `twMerge` API in both; no SDK code change required.
50
-
51
- ## [0.3.2] — 2026-04-19
52
-
53
- ### Fixed (revert of accidental change in 0.3.0 / 0.3.1)
54
- - **`astralkit/theme` export restored to the Tailwind v3 file (`astralkit-theme.css`, `:root` syntax).** This matches the 0.2.x default and is the designed behavior: v3 is the primary customer base, so the default export targets v3. Projects that pinned `0.3.0` or `0.3.1` saw this default silently flip to v4, which broke any v3 project with `@import "astralkit/theme"` in its CSS.
55
- - `astralkit/theme-v4` export unchanged — still the explicit opt-in for Tailwind v4 projects.
56
- - Removed the short-lived `astralkit/theme-v3` alias introduced in 0.3.0/0.3.1. If you added it to your CSS during that window, change it back to `astralkit/theme`.
57
-
58
- ### Migrating from 0.3.0 / 0.3.1
59
- - **Tailwind v3 projects**: no action your existing `@import "astralkit/theme"` now resolves to the v3 file again, as it did in 0.2.x.
60
- - **Tailwind v4 projects**: ensure your CSS uses `@import "astralkit/theme-v4"` (not `"astralkit/theme"`). The AstralKit main app and `astralkit init` for v4 projects already use the explicit `theme-v4` form.
61
-
62
- ## [0.3.1] 2026-04-18 (superseded do not use for new installs)
63
-
64
- ### Added
65
- - `peerDependencies` declaration: `tailwindcss >= 3.0.0`. Installing `astralkit` in a project without Tailwind now surfaces a clear peer-dep warning instead of silent breakage.
66
- - File header comment on `astralkit-theme.css` marking it as the Tailwind v3 file.
67
-
68
- ### Known issue (fixed in 0.3.2)
69
- - The `astralkit/theme` export was flipped to resolve to the v4 file — unintentional. Any v3 project that upgraded from `0.2.x` silently started pulling v4 CSS. Use `0.3.2`.
70
-
71
- ## [0.3.0] 2026-04-18 (superseded do not use for new installs)
72
-
73
- ### Added
74
- - v4 theme refinements across 12 commits of token architecture work (rail/panel elevated colors, sidebar tokens, avatar sizes, Phase A standardization).
75
- - `primitives/.npmignore` excludes `*.backup` and `*.pre-v4-split` scratch files from published tarballs (~220 kB removed).
76
-
77
- ### Fixed
78
- - Tailwind v3 plugin registration (via CLI init) now covers additional `plugins: [...]` formatting variants.
79
-
80
- ### Known issue (fixed in 0.3.2)
81
- - Same `astralkit/theme` export mis-resolution as 0.3.1. Use `0.3.2`.
82
-
83
- ## [0.2.0] — 2026-04-02
84
-
85
- ### Added
86
- - Initial public release on npm.
87
- - Design tokens (theme CSS), utilities CSS, palette presets, primitives folder, `cn()` helper, Tailwind v3/v4 configs.
1
+ # Changelog
2
+
3
+ All notable changes to the `astralkit` SDK package.
4
+
5
+ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
6
+ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
+
8
+ ## [0.8.0] — 2026-08-23
9
+
10
+ ### Changed (BREAKING — spacing grammar renumbered)
11
+ - **The ak spacing scale now uses Tailwind's core 4px-grid numbering.** `ak-N` = core `N` semantics: `ak-1`=4px, `ak-2`=8px, `ak-3`=12px, `ak-4`=16px, `ak-6`=24px `ak-48`=192px. Values are UNCHANGED names moved onto the numbering every AI coder and Tailwind user already knows, eliminating the underscore-fraction gotcha family (`ak-1_5` et al.).
12
+ - The two off-grid steps left the ak namespace: 6px is core `1.5` (`p-1.5`), 10px is core `2.5` identical pixels, standard spelling.
13
+ - Old fraction names (`ak-0_5`…`ak-5_5`, dot variants in v3) remain as DEPRECATED aliases at their original values; removal planned for 1.0. Old INTEGER names could not be aliased (they collide with the new grammar) — code written against pre-0.8 integers must be migrated (`tools/spacing-migration/rename-map.py` in the AstralKit repo does it in one pass).
14
+
15
+ ## [0.7.0] — 2026-08-22
16
+
17
+ ### Added
18
+ - **Material utilities** — `ak-material-surface`, `ak-material-control`, refined `ak-dark-material`: the opaque elevated material surfaces the kanban/core component sets use for modals, drawers, and floating controls. Components built against these rendered **transparent overlays** on 0.6.0 (found live via the kanban-01 task drawer).
19
+ - **Semantic font utilities** — `ak-font-heading`, `ak-font-label`, `ak-font-ui`, `ak-font-ui-strong`, `ak-font-body`, backed by new font-dial variables (`--font-ak-heading` etc., with the previous literal stacks as fallbacks) so a theme can re-font at runtime.
20
+ - **Radix animation helpers** — `ak-overlay-anim`, `ak-pop-anim`, `ak-sheet-anim`, `ak-accordion-anim`, `ak-collapsible-anim`.
21
+ - **Control primitives** — `ak-control-track`, `ak-control-thumb`, `ak-control-knob`; plus `ak-button-group`(+`-separator`), `ak-scrollbar`, `ak-quiet-hover`.
22
+ - **`astralkit/presets` export** — appearance presets, theme palettes, chart palettes, font pairings, dials, and materials as data (the role system + font library per the no-font-dials-in-builder decision).
23
+ - **`ak-hover-shimmer`** animation (+ `ak-hover-shimmer-sweep` keyframes).
24
+ - **Error-role hover tokens** — `ak-error-hover`, `ak-danger-hover`.
25
+
26
+ ### Changed
27
+ - `font-ak-sans`/`-serif`/`-mono` (v3 plugin) are now var-driven (`var(--font-ak-sans, Inter)` …) so containers can re-font at runtime; literal stacks remain as fallbacks — no visual change for existing consumers.
28
+ - `ak-focus-ring` implementation refined.
29
+
30
+ ## [0.6.0] — 2026-07-06
31
+
32
+ ### Added
33
+ - **`astralkit/theme-context` export** — `AkThemeProvider` / `useAkTheme`, the React context that propagates per-component dark mode across Radix portal boundaries (Dialog/DropdownMenu/Popover content portals to `document.body`, escaping the `data-ak-dark-*` attribute scope). Installable components now import this from the SDK instead of shipping a local provider file. Adds `react >= 18` as an **optional** peer dependency — CSS-only consumers are unaffected.
34
+ - **Sidebar theming layer** (authored post-0.5.0, first published here): `primitives/sidebar.css`, `ak-dark-material` / `ak-mirror-shimmer` and `ak-sidebar-*` utilities, plus the gradient / selection / inverse / surface-container token extensions the themed sidebar set depends on.
35
+
36
+ ## [0.5.0] — 2026-06-12
37
+
38
+ ### Added (Material 3 role grammar)
39
+ - **45 new color-role tokens across both the v4 `@theme` and the v3 Tailwind plugin** (full v3/v4 parity). These complete the M3 role grammar that a large set of components now depend on:
40
+ - **Surface containers** `surface-3`, `surface-4`, `surface-container`, `surface-container-low`/`-lowest`/`-high`/`-highest`.
41
+ - **Inverse** `inverse-surface`, `inverse-on-surface` (dark cards on light themes and vice-versa).
42
+ - **Secondary / tertiary / accent / error roles** — `secondary`(+`-container`), `on-secondary`(+`-container`), `tertiary`(+`-container`), `on-tertiary`(+`-container`), `accent`, `accent-soft`, `on-accent`, `error`, `error-container`, `on-error`, `on-error-container`, plus `primary-container`/`on-primary-container`.
43
+ - **Surface / outline** `on-surface`, `on-surface-variant`, `outline`, `outline-variant`, `scrim`.
44
+ - **Per-theme controls** `slider-fill`, `slider-ring` (themed Radix slider fill/ring).
45
+ - **Status badges** — `status-{new,beta,stable,deprecated}-{bg,border,text}`.
46
+
47
+ ### Fixed
48
+ - **`ak-skeleton` shimmer now respects `prefers-reduced-motion`.** Added a `@media (prefers-reduced-motion: reduce)` guard that stops the looping shimmer on `.ak-skeleton::after`.
49
+
50
+ ## [0.4.0] — 2026-06-06
51
+
52
+ ### Added
53
+ - **`astralkit/motion`** — accessible Framer Motion presets tuned to the AstralKit motion tokens (`fadeInUp`, `fadeIn`, `scaleIn`, `staggerContainer`/`staggerItem`, `revealOnScroll`, `hoverLift`/`pressable`, `akTransition`, and `withReducedMotion`). Plain variant/transition objects — importing adds **no dependency**; bring your own `motion` (MIT). All presets are `prefers-reduced-motion`-safe via `withReducedMotion`.
54
+
55
+ ### Changed
56
+ - **Motion policy reversed: Framer Motion is now allowed.** The previous "no Framer Motion" rule was based on a licensing misunderstanding — the `motion` package is MIT. `ai-rules.md` now permits Framer Motion + CSS + Lenis and points to the `astralkit/motion` presets; **GSAP** is the disallowed one (its license restricts sold products/templates).
57
+ - `ai-rules.md`: motion guidance updated accordingly; premium-effect toolkit (`ak-card-glow`, `ak-mesh-*`, `ak-float`, `ak-scroll-fade`, etc.) emphasized for richer output.
58
+
59
+ ## [0.3.8]2026-06-06
60
+
61
+ ### Fixed
62
+ - **Body font corrected to Inter.** `--font-ak-sans` was `'DM Sans'` in `astralkit-theme.css`, `astralkit-theme-v4.css`, and the Tailwind plugin, contradicting the canonical Inter body font. Replaced with `'Inter'` everywhere.
63
+ - **Tailwind v3 plugin export repointed to `tailwind.cjs`.** `astralkit/tailwind` resolved to a stale `tailwind.js` that was both an incomplete token subset and broken under the package's `"type": "module"` (it used CommonJS `require()`). Removed `tailwind.js`; `astralkit/tailwind` now resolves to the complete `tailwind.cjs`. Single source of truth for v3 utilities.
64
+
65
+ ### Added (v3 plugin token parity with v4)
66
+ - Registered every token the v4 `@theme` auto-generates but the v3 plugin was missing: colors (`surface-raised`/`-soft`, `surface-glass`/`-strong`, `highlight-soft`/`-strong`, `skeleton-base`/`-shine`, `sheet-handle`, `pink`/`pink-subtle`), avatar/badge text sizes, spacing `ak-9`/`ak-11`/`ak-14`, `rounded-ak-xs`, `duration-ak-skeleton`, and `size-ak-avatar-xs`. v3 and v4 now expose an identical utility surface.
67
+
68
+ ## [0.3.3] — 2026-04-22
69
+
70
+ ### Changed
71
+ - Widened `tailwind-merge` dependency range from `^2.2.0` to `^2.2.0 || ^3.0.0`. Tailwind CSS v4 projects use `tailwind-merge@v3` (which adds v4 class-name recognition), so accepting either major version lets npm dedupe to the host project's copy instead of nesting a second `node_modules/astralkit/node_modules/tailwind-merge`. Same `twMerge` API in both; no SDK code change required.
72
+
73
+ ## [0.3.2] — 2026-04-19
74
+
75
+ ### Fixed (revert of accidental change in 0.3.0 / 0.3.1)
76
+ - **`astralkit/theme` export restored to the Tailwind v3 file (`astralkit-theme.css`, `:root` syntax).** This matches the 0.2.x default and is the designed behavior: v3 is the primary customer base, so the default export targets v3. Projects that pinned `0.3.0` or `0.3.1` saw this default silently flip to v4, which broke any v3 project with `@import "astralkit/theme"` in its CSS.
77
+ - `astralkit/theme-v4` export unchanged — still the explicit opt-in for Tailwind v4 projects.
78
+ - Removed the short-lived `astralkit/theme-v3` alias introduced in 0.3.0/0.3.1. If you added it to your CSS during that window, change it back to `astralkit/theme`.
79
+
80
+ ### Migrating from 0.3.0 / 0.3.1
81
+ - **Tailwind v3 projects**: no action — your existing `@import "astralkit/theme"` now resolves to the v3 file again, as it did in 0.2.x.
82
+ - **Tailwind v4 projects**: ensure your CSS uses `@import "astralkit/theme-v4"` (not `"astralkit/theme"`). The AstralKit main app and `astralkit init` for v4 projects already use the explicit `theme-v4` form.
83
+
84
+ ## [0.3.1] — 2026-04-18 (superseded — do not use for new installs)
85
+
86
+ ### Added
87
+ - `peerDependencies` declaration: `tailwindcss >= 3.0.0`. Installing `astralkit` in a project without Tailwind now surfaces a clear peer-dep warning instead of silent breakage.
88
+ - File header comment on `astralkit-theme.css` marking it as the Tailwind v3 file.
89
+
90
+ ### Known issue (fixed in 0.3.2)
91
+ - The `astralkit/theme` export was flipped to resolve to the v4 file — unintentional. Any v3 project that upgraded from `0.2.x` silently started pulling v4 CSS. Use `0.3.2`.
92
+
93
+ ## [0.3.0] — 2026-04-18 (superseded — do not use for new installs)
94
+
95
+ ### Added
96
+ - v4 theme refinements across 12 commits of token architecture work (rail/panel elevated colors, sidebar tokens, avatar sizes, Phase A standardization).
97
+ - `primitives/.npmignore` — excludes `*.backup` and `*.pre-v4-split` scratch files from published tarballs (~220 kB removed).
98
+
99
+ ### Fixed
100
+ - Tailwind v3 plugin registration (via CLI init) now covers additional `plugins: [...]` formatting variants.
101
+
102
+ ### Known issue (fixed in 0.3.2)
103
+ - Same `astralkit/theme` export mis-resolution as 0.3.1. Use `0.3.2`.
104
+
105
+ ## [0.2.0] — 2026-04-02
106
+
107
+ ### Added
108
+ - Initial public release on npm.
109
+ - Design tokens (theme CSS), utilities CSS, palette presets, primitives folder, `cn()` helper, Tailwind v3/v4 configs.
package/LICENSE CHANGED
@@ -1,34 +1,73 @@
1
- AstralKit License
2
-
3
- Copyright (c) 2025-2026 Blue Beacon Creative LLC. All rights reserved.
4
-
5
- This software and associated files (the "Software") are the proprietary
6
- intellectual property of Blue Beacon Creative LLC. The Software is licensed,
7
- not sold.
8
-
9
- The design tokens and CSS utilities included in this package are freely usable
10
- in any project that uses AstralKit components. Components, boosters, and
11
- workflows installed via the AstralKit CLI are governed by the AstralKit End
12
- User License Agreement.
13
-
14
- PROHIBITED USES
15
-
16
- You may NOT, without the express prior written consent of Blue Beacon Creative LLC:
17
-
18
- 1. Use the Software's source code as training data, fine-tuning data, or input
19
- for any artificial intelligence system, machine learning model, large language
20
- model, neural network, or any automated system designed to generate code,
21
- text, images, or other output.
22
-
23
- 2. Resell, sublicense, or redistribute the Software as a standalone product,
24
- design system, or token library.
25
-
26
- 3. Build a competing product using the Software's design tokens, CSS
27
- architecture, or utility system.
28
-
29
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
30
- IMPLIED. IN NO EVENT SHALL BLUE BEACON CREATIVE LLC BE LIABLE FOR ANY CLAIM,
31
- DAMAGES OR OTHER LIABILITY.
32
-
33
- Full license terms: https://astralkit.com/license
34
- Contact: hello@astralkit.com
1
+ AstralKit SDK License
2
+
3
+ Copyright (c) 2025-2026 Blue Beacon Creative LLC.
4
+
5
+ This package contains the AstralKit design token system, utility classes, and
6
+ component primitives (the "SDK"). It does NOT include AstralKit components,
7
+ boosters, workflows, or launchpads, which are licensed separately (see below).
8
+
9
+
10
+ 1. FREE USE GRANT
11
+
12
+ You may use the SDK free of charge, without an account, in any number of
13
+ projects — personal or commercial, closed source or open source, for yourself
14
+ or for clients. No attribution is required. There is no requirement that your
15
+ project also use AstralKit components.
16
+
17
+ You may modify the SDK for use within your own projects.
18
+
19
+
20
+ 2. DESIGN TOKENS ARE MIT LICENSED
21
+
22
+ The design token layer — the CSS custom properties defining colors, type and
23
+ spacing scales, radii, sizes, shadows, and motion is additionally available
24
+ under the MIT License, distributed as `astralkit-tokens.css` via
25
+ https://cdn.astralkit.com. Use of that file is governed by MIT terms only, and
26
+ nothing in section 3 restricts it.
27
+
28
+
29
+ 3. RESTRICTIONS
30
+
31
+ You may NOT, without express prior written consent of Blue Beacon Creative LLC:
32
+
33
+ a. Repackage or redistribute the SDK — in whole or in substantial part — as a
34
+ standalone design system, token library, UI kit, theme, or CSS framework,
35
+ whether free or paid. (Using the SDK inside a website or application you
36
+ build is expressly permitted; redistributing it AS the product is not.)
37
+
38
+ b. Build a product that competes with AstralKit using the SDK's component
39
+ primitives or CSS architecture.
40
+
41
+ These restrictions do not apply to `astralkit-tokens.css` (see section 2).
42
+
43
+
44
+ 4. AI AND MACHINE LEARNING
45
+
46
+ Use of the SDK as training data for AI systems, machine learning models, and
47
+ large language models is permitted. AstralKit is designed to be agent-native;
48
+ we want AI tools to know this design language.
49
+
50
+ This permission covers the SDK only. AstralKit components, boosters, workflows,
51
+ and launchpads are excluded — see their license.
52
+
53
+
54
+ 5. COMPONENTS, BOOSTERS, WORKFLOWS, AND LAUNCHPADS
55
+
56
+ Content installed via the AstralKit CLI or MCP server — components, boosters,
57
+ workflows, and launchpads — is NOT covered by this license. It is governed by
58
+ the AstralKit End User License Agreement at https://astralkit.com/license,
59
+ which restricts redistribution, competing use, and AI training.
60
+
61
+
62
+ 6. NO WARRANTY
63
+
64
+ THE SDK IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
65
+ INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
66
+ PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL BLUE BEACON CREATIVE
67
+ LLC BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
68
+ OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
69
+ SDK OR THE USE OR OTHER DEALINGS IN THE SDK.
70
+
71
+
72
+ Full terms: https://astralkit.com/license
73
+ Contact: hello@astralkit.com
package/README.md CHANGED
@@ -66,6 +66,36 @@ export function Button({ className, ...props }) {
66
66
  - [CSS Variables Reference](https://astralkit.com/documentation/css-variables-reference)
67
67
  - [Theming & Customization](https://astralkit.com/documentation/theming-customization)
68
68
 
69
+ ## CDN (no build step)
70
+
71
+ For plain HTML pages, load the CSS directly — no npm, no Tailwind, no build:
72
+
73
+ ```html
74
+ <link rel="preconnect" href="https://fonts.googleapis.com">
75
+ <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
76
+ <link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800&family=DM+Serif+Display&family=JetBrains+Mono:wght@400;500;600;700&display=swap" rel="stylesheet">
77
+ <link rel="stylesheet" href="https://cdn.astralkit.com/v0.6.0/astralkit.min.css">
78
+ ```
79
+
80
+ | CDN file | Contents |
81
+ |---|---|
82
+ | `astralkit.min.css` | Tokens + `ak-*` utilities + component primitives |
83
+ | `astralkit-tokens.min.css` | Design tokens only (**MIT licensed**) |
84
+ | `astralkit-palettes.min.css` | Curated palettes — set `data-ak-theme="…"` |
85
+
86
+ Dark mode: `data-theme="dark"` on `<html>`. Fonts are intentionally not bundled
87
+ (an `@import` inside CSS is render-blocking) — add the `<link>` tags above.
88
+
69
89
  ## License
70
90
 
71
- Proprietary[AstralKit License](https://astralkit.com/license)
91
+ **This SDK is free to use** any project, commercial or personal, closed or
92
+ open source, no account required. The **design tokens are MIT licensed**
93
+ (`astralkit-tokens.css`). Training AI models on this SDK is permitted.
94
+
95
+ You may not repackage or redistribute the SDK as a competing design system,
96
+ token library, or UI kit.
97
+
98
+ AstralKit components, boosters, workflows, and launchpads are **licensed
99
+ separately** under the [AstralKit EULA](https://astralkit.com/license).
100
+
101
+ Full terms: [`LICENSE`](./LICENSE) · [astralkit.com/license](https://astralkit.com/license)