create-claude-workspace 1.1.94 → 1.1.95

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.
Files changed (5) hide show
  1. package/dist/template/.claude/profiles/angular.md +4 -0
  2. package/dist/template/.claude/profiles/react.md +4 -0
  3. package/dist/template/.claude/profiles/svelte.md +4 -0
  4. package/dist/template/.claude/profiles/vue.md +4 -0
  5. package/package.json +1 -1
package/dist/template/.claude/profiles/angular.md CHANGED
@@ -355,6 +355,10 @@ Then run `<PM> install` to create the link. SCSS `@use 'theme/colors'` (or `@use
355
355
 
356
356
  **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.
357
357
 
358
+ **What lives where:**
359
+ - **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.**
360
+ - **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.
361
+
358
362
  **Token source (pick one):**
359
363
  - **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`
360
364
  - **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/react.md CHANGED
@@ -245,6 +245,10 @@ Then run `<PM> install` to create the link. SCSS `@use 'theme/colors'` (or `@use
245
245
 
246
246
  **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.
247
247
 
248
+ **What lives where:**
249
+ - **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.**
250
+ - **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.
251
+
248
252
  **Token source (pick one):**
249
253
  - **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`
250
254
  - **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 CHANGED
@@ -245,6 +245,10 @@ Then run `<PM> install` to create the link. SCSS `@use 'theme/colors'` (or `@use
245
245
 
246
246
  **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.
247
247
 
248
+ **What lives where:**
249
+ - **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.**
250
+ - **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.
251
+
248
252
  **Token source (pick one):**
249
253
  - **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`
250
254
  - **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 CHANGED
@@ -273,6 +273,10 @@ Then run `<PM> install` to create the link. SCSS `@use 'theme/colors'` (or `@use
273
273
 
274
274
  **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.
275
275
 
276
+ **What lives where:**
277
+ - **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.**
278
+ - **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.
279
+
276
280
  **Token source (pick one):**
277
281
  - **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`
278
282
  - **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 CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "create-claude-workspace",
3
- "version": "1.1.94",
3
+ "version": "1.1.95",
4
4
  "description": "Scaffold a project with Claude Code agents for autonomous AI-driven development",
5
5
  "type": "module",
6
6
  "bin": {