create-claude-workspace 1.1.91 → 1.1.93

package/dist/template/.claude/agents/backend-ts-architect.md

@@ -86,7 +86,7 @@ Always prefer `@cibule/*` packages over custom implementations:
 - `moduleResolution: "bundler"` — NEVER add `.js` extensions to imports (write `'./foo'`, not `'./foo.js'`)
 - `readonly` on all fields that don't need reassignment
 - Custom error classes for domain-specific errors
-- Input validation at system boundaries — **TypeBox** preferred (compile-time types + runtime validation from one schema, no duplication). Use `typebox` and `typebox/compiler` for `TypeCompiler`.
+- Input validation at system boundaries — **TypeBox** preferred (compile-time types + runtime validation from one schema, no duplication). Use `typebox` and `typebox/compiler` for `TypeCompiler`. **NEVER use `@sinclair/typebox`** — the correct package is `typebox` (renamed).
 - Async/await patterns (no callback hell)
 - Separation of concerns (routes, services, repositories)
 - File size limit: MAX 200 lines per TypeScript file

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

@@ -334,22 +334,26 @@ npx themecraft generate    # generates type-safe SCSS from tokens.json
 
 **Making theme resolvable by package name (MANDATORY):**
 
-Add the theme library as a workspace dependency in `package.json` so SCSS resolves `@use 'theme/...'` from `node_modules`:
+The path MUST point to the **library root directory** (where `package.json` lives). The SCSS compiler resolves `@use 'theme/colors'` via `package.json` `exports` field — just like Node.js resolves JS imports. The library's `package.json` maps export paths (e.g., `./colors`) to actual SCSS files (e.g., `./src/generated/theme/_colors.scss`).
+
 ```jsonc
 // package.json (root or consuming app)
 {
   "dependencies": {
-    "theme": "workspace:./libs/shared/ui/theme"       // pnpm/bun
-    // or "file:./libs/shared/ui/theme" for npm
-    // If repo has a scope: "@[scope]/theme": "workspace:./libs/shared/ui/theme"
+    "theme": "workspace:./libs/ui/theme"       // pnpm/bun
+    // or "file:./libs/ui/theme" for npm
+    // If repo has a scope: "@[scope]/theme": "workspace:./libs/ui/theme"
   }
 }
 ```
+
+**NEVER point to a subdirectory** like `./libs/ui/theme/src/generated/theme` or `./libs/ui/theme/src` — always the library root with `package.json`. The `exports` field in that `package.json` handles the mapping.
+
 Then run `<PM> install` to create the link. SCSS `@use 'theme/colors'` (or `@use '@[scope]/theme/colors'` with scope) resolves automatically.
 
 **NEVER use `stylePreprocessorOptions.includePaths`** — workspace dependency is the only supported approach. `includePaths` breaks IDE autocomplete, makes imports ambiguous, and doesn't survive refactoring.
 
-**How it works:** `npx themecraft generate` runs inside the theme library (`libs/shared/ui/theme/`) and produces typed SCSS files (`src/colors.scss`, `sizes.scss`, `typography.scss`) that wrap `color-var()`/`size-var()` internally. Because the library is linked as a package, `@use 'theme/colors'` resolves to these generated files. Components consume the generated variables — never the raw accessor functions, never `generated/` paths.
+**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.
 
 **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`

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

@@ -224,22 +224,26 @@ npx themecraft generate    # generates type-safe SCSS from tokens.json
 
 **Making theme resolvable by package name (MANDATORY):**
 
-Add the theme library as a workspace dependency in `package.json` so SCSS resolves `@use 'theme/...'` from `node_modules`:
+The path MUST point to the **library root directory** (where `package.json` lives). The SCSS compiler resolves `@use 'theme/colors'` via `package.json` `exports` field — just like Node.js resolves JS imports. The library's `package.json` maps export paths (e.g., `./colors`) to actual SCSS files (e.g., `./src/generated/theme/_colors.scss`).
+
 ```jsonc
 // package.json (root or consuming app)
 {
   "dependencies": {
-    "theme": "workspace:./libs/shared/ui/theme"       // pnpm/bun
-    // or "file:./libs/shared/ui/theme" for npm
-    // If repo has a scope: "@[scope]/theme": "workspace:./libs/shared/ui/theme"
+    "theme": "workspace:./libs/ui/theme"       // pnpm/bun
+    // or "file:./libs/ui/theme" for npm
+    // If repo has a scope: "@[scope]/theme": "workspace:./libs/ui/theme"
   }
 }
 ```
+
+**NEVER point to a subdirectory** like `./libs/ui/theme/src/generated/theme` or `./libs/ui/theme/src` — always the library root with `package.json`. The `exports` field in that `package.json` handles the mapping.
+
 Then run `<PM> install` to create the link. SCSS `@use 'theme/colors'` (or `@use '@[scope]/theme/colors'` with scope) resolves automatically.
 
 **NEVER use `sassOptions.includeDirs` or `css.preprocessorOptions.scss.includePaths`** — workspace dependency is the only supported approach.
 
-**How it works:** `npx themecraft generate` runs inside the theme library and produces typed SCSS files (`src/colors.scss`, `sizes.scss`, `typography.scss`) that wrap `color-var()`/`size-var()` internally. Because the library is linked as a package, `@use 'theme/colors'` resolves to these generated files. Components consume the generated variables — never the raw accessor functions, never `generated/` paths.
+**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.
 
 **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`

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

@@ -224,22 +224,26 @@ npx themecraft generate    # generates type-safe SCSS from tokens.json
 
 **Making theme resolvable by package name (MANDATORY):**
 
-Add the theme library as a workspace dependency in `package.json` so SCSS resolves `@use 'theme/...'` from `node_modules`:
+The path MUST point to the **library root directory** (where `package.json` lives). The SCSS compiler resolves `@use 'theme/colors'` via `package.json` `exports` field — just like Node.js resolves JS imports. The library's `package.json` maps export paths (e.g., `./colors`) to actual SCSS files (e.g., `./src/generated/theme/_colors.scss`).
+
 ```jsonc
 // package.json (root or consuming app)
 {
   "dependencies": {
-    "theme": "workspace:./libs/shared/ui/theme"       // pnpm/bun
-    // or "file:./libs/shared/ui/theme" for npm
-    // If repo has a scope: "@[scope]/theme": "workspace:./libs/shared/ui/theme"
+    "theme": "workspace:./libs/ui/theme"       // pnpm/bun
+    // or "file:./libs/ui/theme" for npm
+    // If repo has a scope: "@[scope]/theme": "workspace:./libs/ui/theme"
   }
 }
 ```
+
+**NEVER point to a subdirectory** like `./libs/ui/theme/src/generated/theme` or `./libs/ui/theme/src` — always the library root with `package.json`. The `exports` field in that `package.json` handles the mapping.
+
 Then run `<PM> install` to create the link. SCSS `@use 'theme/colors'` (or `@use '@[scope]/theme/colors'` with scope) resolves automatically.
 
 **NEVER use `css.preprocessorOptions.scss.includePaths`** — workspace dependency is the only supported approach.
 
-**How it works:** `npx themecraft generate` runs inside the theme library and produces typed SCSS files (`src/colors.scss`, `sizes.scss`, `typography.scss`) that wrap `color-var()`/`size-var()` internally. Because the library is linked as a package, `@use 'theme/colors'` resolves to these generated files. Components consume the generated variables — never the raw accessor functions, never `generated/` paths.
+**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.
 
 **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`

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

@@ -252,22 +252,26 @@ npx themecraft generate    # generates type-safe SCSS from tokens.json
 
 **Making theme resolvable by package name (MANDATORY):**
 
-Add the theme library as a workspace dependency in `package.json` so SCSS resolves `@use 'theme/...'` from `node_modules`:
+The path MUST point to the **library root directory** (where `package.json` lives). The SCSS compiler resolves `@use 'theme/colors'` via `package.json` `exports` field — just like Node.js resolves JS imports. The library's `package.json` maps export paths (e.g., `./colors`) to actual SCSS files (e.g., `./src/generated/theme/_colors.scss`).
+
 ```jsonc
 // package.json (root or consuming app)
 {
   "dependencies": {
-    "theme": "workspace:./libs/shared/ui/theme"       // pnpm/bun
-    // or "file:./libs/shared/ui/theme" for npm
-    // If repo has a scope: "@[scope]/theme": "workspace:./libs/shared/ui/theme"
+    "theme": "workspace:./libs/ui/theme"       // pnpm/bun
+    // or "file:./libs/ui/theme" for npm
+    // If repo has a scope: "@[scope]/theme": "workspace:./libs/ui/theme"
   }
 }
 ```
+
+**NEVER point to a subdirectory** like `./libs/ui/theme/src/generated/theme` or `./libs/ui/theme/src` — always the library root with `package.json`. The `exports` field in that `package.json` handles the mapping.
+
 Then run `<PM> install` to create the link. SCSS `@use 'theme/colors'` (or `@use '@[scope]/theme/colors'` with scope) resolves automatically.
 
 **NEVER use `css.preprocessorOptions.scss.includePaths`** — workspace dependency is the only supported approach.
 
-**How it works:** `npx themecraft generate` runs inside the theme library and produces typed SCSS files (`src/colors.scss`, `sizes.scss`, `typography.scss`) that wrap `color-var()`/`size-var()` internally. Because the library is linked as a package, `@use 'theme/colors'` resolves to these generated files. Components consume the generated variables — never the raw accessor functions, never `generated/` paths.
+**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.
 
 **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`

package/dist/template/.claude/templates/claude-md.md

@@ -320,7 +320,7 @@ Key rules enforced (do NOT weaken):
 
 [Include only if the project has a backend]
 
-- Hono routes with validation (**TypeBox** — `typebox` for schema + type inference, `TypeCompiler` for runtime validation)
+- Hono routes with validation (**TypeBox** — `typebox` for schema + type inference, `TypeCompiler` for runtime validation). **NEVER use `@sinclair/typebox`** — the correct package is `typebox`.
 - **OpenAPI-first**: Use `hono-openapi` with `openAPIRouteHandler` for all API routes — generates OpenAPI spec from TypeBox schemas automatically. API docs served via `@scalar/hono-api-reference` at `/reference`.
 - `@cibule/di` for dependency injection (see @cibule/* Ecosystem section above)
 - `@cibule/db` + driver for database access, UnitOfWork for atomic writes

package/package.json

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