create-claude-workspace 1.1.93 → 1.1.95

package/dist/template/.claude/profiles/angular.md

@@ -306,7 +306,7 @@ npx themecraft generate    # generates type-safe SCSS from tokens.json
 **Pipeline:**
 1. `tokens.json` — define token names (colors, sizes, typography, breakpoints) with JSON schema validation
 2. `npx themecraft generate` — produces type-safe SCSS variables with IDE autocomplete
-3. Theme files (`themes/light.scss`, `dark.scss`) — use `define-light-theme()` / `define-dark-theme()` with token value maps
+3. Theme values files (`themes/light-values.scss`, `dark-values.scss`) + single entry point (`themes/themes.scss`) with ALL themes
 4. `@themecraft/core/themes` → `variables()` mixin emits CSS custom properties at `:root`
 5. `@themecraft/angular` → `provideTheme()` for runtime switching, `provideThemeServer()` for SSR (no FOUC)
 
@@ -355,13 +355,19 @@ Then run `<PM> install` to create the link. SCSS `@use 'theme/colors'` (or `@use
 
 **How it works:** `npx themecraft generate` runs inside the theme library and produces typed SCSS files (e.g., `src/generated/theme/_colors.scss`, `_sizes.scss`, `_typography.scss`) that wrap `color-var()`/`size-var()` internally. The library's `package.json` `exports` field maps `./colors` → `./src/generated/theme/_colors.scss` etc. Because the library is linked as a workspace dependency, `@use 'theme/colors'` resolves through `node_modules/theme/package.json` exports. Components consume the generated variables — never the raw accessor functions, never `generated/` paths, never subdirectory links.
 
+**What lives where:**
+- **Theme library** (`libs/ui/theme/`) — ONLY `tokens.json`, `themecraft.config.json`, `package.json` with `exports`, and generated SCSS files (output of `npx themecraft generate`). **NEVER put theme values files, entry points, or global styles here.**
+- **Application** (`apps/[app]/src/`) — theme values files (`themes/light-values.scss`, `dark-values.scss`), single theme entry point (`themes/themes.scss`), global styles (`styles.scss`). These are app-specific — different apps can define different themes using the same shared tokens.
+
 **Token source (pick one):**
 - **With Figma:** `npx themecraft sync --figma-file-key YOUR_FILE_KEY --token YOUR_ACCESS_TOKEN` pulls design variables into `tokens.json`, then `npx themecraft generate`
 - **Without Figma:** `npx themecraft init` creates `tokens.json` scaffold → manually define token names (color groups, size groups, typography levels) → `npx themecraft generate`
 
 Either way, the result is the same: typed SCSS files inside the theme library, importable via `@use 'theme/colors'`.
 
-**Theme values** (`themes/light-values.scss`) — define a `$theme` variable with token values:
+**Theme values files** — one file per theme, each exports a `$theme` variable:
+
+`themes/light-values.scss`:
 ```scss
 @use '@themecraft/core/theming' as theming;
 @use 'theme/variables/colors';
@@ -389,10 +395,30 @@ $theme: theming.define-light-theme((
 ));
 ```
 
-**Theme entry point** (`themes/light.scss`) — passes values to the engine, compiles to CSS:
+`themes/dark-values.scss`:
+```scss
+@use '@themecraft/core/theming' as theming;
+@use 'theme/variables/colors';
+// ... same imports
+
+$theme: theming.define-dark-theme((
+  color: theming.define-color-scheme((
+    colors.$background-body: #1a1a2e,
+    colors.$content-primary: #e0e0e0,
+    colors.$interactive-primary: #64b5f6,
+  )),
+  // ... sizes, typography, breakpoints
+));
+```
+
+**Single entry point for ALL themes** (`themes/themes.scss`) — compiles to one CSS file with all themes. **NEVER create separate entry points per theme** (e.g., `light.scss`, `dark.scss` each with their own `@include themes.variables`) — that breaks theme switching:
 ```scss
 @use './light-values' as light;
-@use '@themecraft/core/themes' with ($themes: (light: light.$theme));
+@use './dark-values' as dark;
+@use '@themecraft/core/themes' with ($themes: (
+  light: light.$theme,
+  dark: dark.$theme,
+));
 
 @include themes.variables(':root');
 ```

package/dist/template/.claude/profiles/react.md

@@ -197,7 +197,7 @@ npx themecraft generate    # generates type-safe SCSS from tokens.json
 **Pipeline:**
 1. `tokens.json` — define token names (colors, sizes, typography, breakpoints) with JSON schema validation
 2. `npx themecraft generate` — produces type-safe SCSS variables with IDE autocomplete
-3. Theme files (`themes/light.scss`, `dark.scss`) — use `define-light-theme()` / `define-dark-theme()`
+3. Theme values files (`themes/light-values.scss`, `dark-values.scss`) + single entry point (`themes/themes.scss`) with ALL themes — NEVER separate entry points per theme
 4. `@themecraft/core/themes` → `variables()` mixin emits CSS custom properties at `:root`
 5. `ThemeManager` (from `@themecraft/core`) — runtime theme switching, storage persistence, FOUC prevention
 
@@ -245,6 +245,10 @@ Then run `<PM> install` to create the link. SCSS `@use 'theme/colors'` (or `@use
 
 **How it works:** `npx themecraft generate` runs inside the theme library and produces typed SCSS files (e.g., `src/generated/theme/_colors.scss`, `_sizes.scss`, `_typography.scss`) that wrap `color-var()`/`size-var()` internally. The library's `package.json` `exports` field maps `./colors` → `./src/generated/theme/_colors.scss` etc. Because the library is linked as a workspace dependency, `@use 'theme/colors'` resolves through `node_modules/theme/package.json` exports. Components consume the generated variables — never the raw accessor functions, never `generated/` paths, never subdirectory links.
 
+**What lives where:**
+- **Theme library** (`libs/ui/theme/`) — ONLY `tokens.json`, `themecraft.config.json`, `package.json` with `exports`, and generated SCSS files (output of `npx themecraft generate`). **NEVER put theme values files, entry points, or global styles here.**
+- **Application** (`apps/[app]/src/` or `src/`) — theme values files (`themes/light-values.scss`, `dark-values.scss`), single theme entry point (`themes/themes.scss`), global styles. These are app-specific — different apps can define different themes using the same shared tokens.
+
 **Token source (pick one):**
 - **With Figma:** `npx themecraft sync --figma-file-key YOUR_FILE_KEY --token YOUR_ACCESS_TOKEN` pulls design variables into `tokens.json`, then `npx themecraft generate`
 - **Without Figma:** `npx themecraft init` creates `tokens.json` scaffold → manually define token names (color groups, size groups, typography levels) → `npx themecraft generate`

package/dist/template/.claude/profiles/svelte.md

@@ -195,7 +195,7 @@ npx themecraft generate    # generates type-safe SCSS from tokens.json
 **Pipeline:**
 1. `tokens.json` — define token names (colors, sizes, typography, breakpoints)
 2. `npx themecraft generate` — produces type-safe SCSS variables with IDE autocomplete
-3. Theme files (`themes/light.scss`, `dark.scss`) — use `define-light-theme()` / `define-dark-theme()`
+3. Theme values files (`themes/light-values.scss`, `dark-values.scss`) + single entry point (`themes/themes.scss`) with ALL themes — NEVER separate entry points per theme
 4. `@themecraft/core/themes` → `variables()` mixin emits CSS custom properties at `:root`
 5. `ThemeManager` (from `@themecraft/core`) — runtime switching, storage, FOUC prevention
 
@@ -245,6 +245,10 @@ Then run `<PM> install` to create the link. SCSS `@use 'theme/colors'` (or `@use
 
 **How it works:** `npx themecraft generate` runs inside the theme library and produces typed SCSS files (e.g., `src/generated/theme/_colors.scss`, `_sizes.scss`, `_typography.scss`) that wrap `color-var()`/`size-var()` internally. The library's `package.json` `exports` field maps `./colors` → `./src/generated/theme/_colors.scss` etc. Because the library is linked as a workspace dependency, `@use 'theme/colors'` resolves through `node_modules/theme/package.json` exports. Components consume the generated variables — never the raw accessor functions, never `generated/` paths, never subdirectory links.
 
+**What lives where:**
+- **Theme library** (`libs/ui/theme/`) — ONLY `tokens.json`, `themecraft.config.json`, `package.json` with `exports`, and generated SCSS files (output of `npx themecraft generate`). **NEVER put theme values files, entry points, or global styles here.**
+- **Application** (`apps/[app]/src/` or `src/`) — theme values files (`themes/light-values.scss`, `dark-values.scss`), single theme entry point (`themes/themes.scss`), global styles. These are app-specific — different apps can define different themes using the same shared tokens.
+
 **Token source (pick one):**
 - **With Figma:** `npx themecraft sync --figma-file-key YOUR_FILE_KEY --token YOUR_ACCESS_TOKEN` pulls design variables into `tokens.json`, then `npx themecraft generate`
 - **Without Figma:** `npx themecraft init` creates `tokens.json` scaffold → manually define token names (color groups, size groups, typography levels) → `npx themecraft generate`

package/dist/template/.claude/profiles/vue.md

@@ -223,7 +223,7 @@ npx themecraft generate    # generates type-safe SCSS from tokens.json
 **Pipeline:**
 1. `tokens.json` — define token names (colors, sizes, typography, breakpoints)
 2. `npx themecraft generate` — produces type-safe SCSS variables with IDE autocomplete
-3. Theme files (`themes/light.scss`, `dark.scss`) — use `define-light-theme()` / `define-dark-theme()`
+3. Theme values files (`themes/light-values.scss`, `dark-values.scss`) + single entry point (`themes/themes.scss`) with ALL themes — NEVER separate entry points per theme
 4. `@themecraft/core/themes` → `variables()` mixin emits CSS custom properties at `:root`
 5. `ThemeManager` (from `@themecraft/core`) — runtime switching, storage, FOUC prevention
 
@@ -273,6 +273,10 @@ Then run `<PM> install` to create the link. SCSS `@use 'theme/colors'` (or `@use
 
 **How it works:** `npx themecraft generate` runs inside the theme library and produces typed SCSS files (e.g., `src/generated/theme/_colors.scss`, `_sizes.scss`, `_typography.scss`) that wrap `color-var()`/`size-var()` internally. The library's `package.json` `exports` field maps `./colors` → `./src/generated/theme/_colors.scss` etc. Because the library is linked as a workspace dependency, `@use 'theme/colors'` resolves through `node_modules/theme/package.json` exports. Components consume the generated variables — never the raw accessor functions, never `generated/` paths, never subdirectory links.
 
+**What lives where:**
+- **Theme library** (`libs/ui/theme/`) — ONLY `tokens.json`, `themecraft.config.json`, `package.json` with `exports`, and generated SCSS files (output of `npx themecraft generate`). **NEVER put theme values files, entry points, or global styles here.**
+- **Application** (`apps/[app]/src/` or `src/`) — theme values files (`themes/light-values.scss`, `dark-values.scss`), single theme entry point (`themes/themes.scss`), global styles. These are app-specific — different apps can define different themes using the same shared tokens.
+
 **Token source (pick one):**
 - **With Figma:** `npx themecraft sync --figma-file-key YOUR_FILE_KEY --token YOUR_ACCESS_TOKEN` pulls design variables into `tokens.json`, then `npx themecraft generate`
 - **Without Figma:** `npx themecraft init` creates `tokens.json` scaffold → manually define token names (color groups, size groups, typography levels) → `npx themecraft generate`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-claude-workspace",
-  "version": "1.1.93",
+  "version": "1.1.95",
   "description": "Scaffold a project with Claude Code agents for autonomous AI-driven development",
   "type": "module",
   "bin": {