@conduction/theme 1.1.65 → 1.1.66

package/.claude/skills/nlds-new/SKILL.md

@@ -1,48 +1,48 @@
----
-name: nlds-new
-description: Create a new NL Design System token set for an organisation — extracts branding from website/huisstijlhandboek via Playwright
----
-
-Create a new NL Design System token set for: $ARGUMENTS
-
-## Instructions
-
-### Gather required information
-
-If `$ARGUMENTS` is empty or does not contain an organisation name, ask:
-
-1. **"What is the name of the organisation?"** (required — do not proceed until answered)
-
-Once you have the name, ask:
-
-2. **"Should I extract the design from the organisation's website, a huisstijlhandboek (style guide), or both?"**
-
-If the user says **website** or **both**, look up the most likely website URL (e.g. `https://www.<name>.nl/`) and ask:
-
-3. **"Is this the correct website: `<url>`? (or provide the right one)"**
-
-If the user says **huisstijlhandboek**, ask:
-
-4. **"What is the URL of the huisstijlhandboek?"**
-
-If `$ARGUMENTS` already contains a name and URL, confirm both with the user before proceeding.
-
-### Derive identifiers
-
-From the organisation name:
-
-- **slug**: lowercase, spaces replaced with hyphens (e.g. "den-haag", "vng-realisatie")
-- **prefix**: same as slug
-- **fullName**: the proper name (e.g. "Den Haag", "VNG Realisatie")
-- **packageName**: `@nl-design-system-unstable/<slug>-design-tokens`
-- **folderName**: `municipalities/<slug>-design-tokens`
-
-### Execute
-
-Read the shared reference at `conduction-theme/.claude/commands/nlds-reference.md` and follow it from the top:
-
-1. **Extract** — follow the extraction procedure (website and/or huisstijlhandboek as the user requested)
-2. **Create all files** — follow the file creation procedure to create the full token set from scratch
-3. **Update component tokens** — follow the component update mapping to apply extracted values
-4. **Build and test** — follow the build procedure, fix any errors
-5. **Summary** — output the summary as described in the reference
+---
+name: nlds-new
+description: Create a new NL Design System token set for an organisation — extracts branding from website/huisstijlhandboek via Playwright
+---
+
+Create a new NL Design System token set for: $ARGUMENTS
+
+## Instructions
+
+### Gather required information
+
+If `$ARGUMENTS` is empty or does not contain an organisation name, ask:
+
+1. **"What is the name of the organisation?"** (required — do not proceed until answered)
+
+Once you have the name, ask:
+
+2. **"Should I extract the design from the organisation's website, a huisstijlhandboek (style guide), or both?"**
+
+If the user says **website** or **both**, look up the most likely website URL (e.g. `https://www.<name>.nl/`) and ask:
+
+3. **"Is this the correct website: `<url>`? (or provide the right one)"**
+
+If the user says **huisstijlhandboek**, ask:
+
+4. **"What is the URL of the huisstijlhandboek?"**
+
+If `$ARGUMENTS` already contains a name and URL, confirm both with the user before proceeding.
+
+### Derive identifiers
+
+From the organisation name:
+
+- **slug**: lowercase, spaces replaced with hyphens (e.g. "den-haag", "vng-realisatie")
+- **prefix**: same as slug
+- **fullName**: the proper name (e.g. "Den Haag", "VNG Realisatie")
+- **packageName**: `@nl-design-system-unstable/<slug>-design-tokens`
+- **folderName**: `municipalities/<slug>-design-tokens`
+
+### Execute
+
+Read the shared reference at `conduction-theme/.claude/commands/nlds-reference.md` and follow it from the top:
+
+1. **Extract** — follow the extraction procedure (website and/or huisstijlhandboek as the user requested)
+2. **Create all files** — follow the file creation procedure to create the full token set from scratch
+3. **Update component tokens** — follow the component update mapping to apply extracted values
+4. **Build and test** — follow the build procedure, fix any errors
+5. **Summary** — output the summary as described in the reference

package/.claude/skills/nlds-update/SKILL.md

@@ -1,53 +1,53 @@
----
-name: nlds-update
-description: Update an existing NL Design System token set — re-extracts branding from website/huisstijlhandboek and applies changes
----
-
-Update an existing NL Design System token set for: $ARGUMENTS
-
-## Instructions
-
-### Gather required information
-
-If `$ARGUMENTS` is empty or does not contain an organisation name, ask:
-
-1. **"What is the name of the organisation to update?"** (required — do not proceed until answered)
-
-Once you have the name, verify the token set exists at `municipalities/<slug>-design-tokens/`. If it does not exist, tell the user and suggest using `/nlds:new` instead.
-
-Then ask:
-
-2. **"Should I re-extract the design from the organisation's website, a huisstijlhandboek (style guide), or both?"**
-
-If the user says **website** or **both**, look up the website URL from the existing `package.json` (the `"website"` field) and ask:
-
-3. **"Is this still the correct website: `<url>`? (or provide the right one)"**
-
-If the user says **huisstijlhandboek**, ask:
-
-4. **"What is the URL of the huisstijlhandboek?"**
-
-### Derive identifiers
-
-From the existing token set, read `src/config.json` to get:
-
-- **slug**: the `prefix` field
-- **fullName**: the `fullName` field
-- **prefix**: same as slug
-- **packageName**: from `package.json` `name` field
-- **folderName**: `municipalities/<slug>-design-tokens`
-
-### Execute
-
-Read the shared reference at `conduction-theme/.claude/commands/nlds-reference.md` and follow it, **skipping Part B** (file creation):
-
-1. **Extract** (Part A) — follow the extraction procedure (website and/or huisstijlhandboek as the user requested)
-2. **Skip Part B** — files already exist, do not recreate them
-3. **Update component tokens** (Part C) — read existing token files, compare with new extraction data, update only values that changed
-4. **Update brand tokens** — if the extraction reveals new/changed colors or fonts:
-   - Update `color.tokens.json` with any new palette entries
-   - Update `typography.tokens.json` if the font changed
-   - Update `font-size.tokens.json` if sizes changed
-   - Download any new font files to `src/font/` and update `font.scss`
-5. **Build and test** (Part D) — follow the build procedure, fix any errors
-6. **Summary** (Part E) — output the summary, highlighting what changed vs the previous version
+---
+name: nlds-update
+description: Update an existing NL Design System token set — re-extracts branding from website/huisstijlhandboek and applies changes
+---
+
+Update an existing NL Design System token set for: $ARGUMENTS
+
+## Instructions
+
+### Gather required information
+
+If `$ARGUMENTS` is empty or does not contain an organisation name, ask:
+
+1. **"What is the name of the organisation to update?"** (required — do not proceed until answered)
+
+Once you have the name, verify the token set exists at `municipalities/<slug>-design-tokens/`. If it does not exist, tell the user and suggest using `/nlds:new` instead.
+
+Then ask:
+
+2. **"Should I re-extract the design from the organisation's website, a huisstijlhandboek (style guide), or both?"**
+
+If the user says **website** or **both**, look up the website URL from the existing `package.json` (the `"website"` field) and ask:
+
+3. **"Is this still the correct website: `<url>`? (or provide the right one)"**
+
+If the user says **huisstijlhandboek**, ask:
+
+4. **"What is the URL of the huisstijlhandboek?"**
+
+### Derive identifiers
+
+From the existing token set, read `src/config.json` to get:
+
+- **slug**: the `prefix` field
+- **fullName**: the `fullName` field
+- **prefix**: same as slug
+- **packageName**: from `package.json` `name` field
+- **folderName**: `municipalities/<slug>-design-tokens`
+
+### Execute
+
+Read the shared reference at `conduction-theme/.claude/commands/nlds-reference.md` and follow it, **skipping Part B** (file creation):
+
+1. **Extract** (Part A) — follow the extraction procedure (website and/or huisstijlhandboek as the user requested)
+2. **Skip Part B** — files already exist, do not recreate them
+3. **Update component tokens** (Part C) — read existing token files, compare with new extraction data, update only values that changed
+4. **Update brand tokens** — if the extraction reveals new/changed colors or fonts:
+   - Update `color.tokens.json` with any new palette entries
+   - Update `typography.tokens.json` if the font changed
+   - Update `font-size.tokens.json` if sizes changed
+   - Download any new font files to `src/font/` and update `font.scss`
+5. **Build and test** (Part D) — follow the build procedure, fix any errors
+6. **Summary** (Part E) — output the summary, highlighting what changed vs the previous version

package/.gitattributes

@@ -1,64 +1,64 @@
-# Auto detect text files and perform LF normalization
-* text=auto
-
-# Source code - always use LF
-*.js text eol=lf
-*.jsx text eol=lf
-*.ts text eol=lf
-*.tsx text eol=lf
-*.mjs text eol=lf
-*.cjs text eol=lf
-
-# Configuration files - always use LF
-*.json text eol=lf
-*.yml text eol=lf
-*.yaml text eol=lf
-*.toml text eol=lf
-*.xml text eol=lf
-
-# Styles - always use LF
-*.css text eol=lf
-*.scss text eol=lf
-*.sass text eol=lf
-*.less text eol=lf
-
-# HTML and templates - always use LF
-*.html text eol=lf
-*.htm text eol=lf
-*.svg text eol=lf
-
-# Documentation - always use LF
-*.md text eol=lf
-*.txt text eol=lf
-*.rtf text eol=lf
-
-# Docker and shell scripts - always use LF
-Dockerfile text eol=lf
-*.dockerfile text eol=lf
-*.sh text eol=lf
-
-# Git files - always use LF
-.gitattributes text eol=lf
-.gitignore text eol=lf
-.gitmodules text eol=lf
-
-# Windows script files - use CRLF
-*.bat text eol=crlf
-*.cmd text eol=crlf
-*.ps1 text eol=crlf
-
-# Binary files - do not modify
-*.png binary
-*.jpg binary
-*.jpeg binary
-*.gif binary
-*.ico binary
-*.webp binary
-*.pdf binary
-*.woff binary
-*.woff2 binary
-*.ttf binary
-*.eot binary
-*.zip binary
-*.gz binary
-*.tar binary
+# Auto detect text files and perform LF normalization
+* text=auto
+
+# Source code - always use LF
+*.js text eol=lf
+*.jsx text eol=lf
+*.ts text eol=lf
+*.tsx text eol=lf
+*.mjs text eol=lf
+*.cjs text eol=lf
+
+# Configuration files - always use LF
+*.json text eol=lf
+*.yml text eol=lf
+*.yaml text eol=lf
+*.toml text eol=lf
+*.xml text eol=lf
+
+# Styles - always use LF
+*.css text eol=lf
+*.scss text eol=lf
+*.sass text eol=lf
+*.less text eol=lf
+
+# HTML and templates - always use LF
+*.html text eol=lf
+*.htm text eol=lf
+*.svg text eol=lf
+
+# Documentation - always use LF
+*.md text eol=lf
+*.txt text eol=lf
+*.rtf text eol=lf
+
+# Docker and shell scripts - always use LF
+Dockerfile text eol=lf
+*.dockerfile text eol=lf
+*.sh text eol=lf
+
+# Git files - always use LF
+.gitattributes text eol=lf
+.gitignore text eol=lf
+.gitmodules text eol=lf
+
+# Windows script files - use CRLF
+*.bat text eol=crlf
+*.cmd text eol=crlf
+*.ps1 text eol=crlf
+
+# Binary files - do not modify
+*.png binary
+*.jpg binary
+*.jpeg binary
+*.gif binary
+*.ico binary
+*.webp binary
+*.pdf binary
+*.woff binary
+*.woff2 binary
+*.ttf binary
+*.eot binary
+*.zip binary
+*.gz binary
+*.tar binary