@imfusion/web-ui 0.6.4-dev.109.g8d507655 → 0.6.4-dev.116.gbcea6d9a

package/CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## `0.7.0`          2026.09.28
+## `0.7.0`          2026.09.27
 
 ### Highlights
 
@@ -174,7 +174,10 @@ Spinner ignores `color`. Choose a baked variant:
   - The Tokens page is the single place that documents the Storybook token controls, and the token reference shows them like
     the showcase: a side panel on large screens, a drawer on smaller ones.
   - Docs pages end with previous and next links in sidebar order.
-  - Storybook docs render `mermaid` fences as diagrams and GitHub alerts as Callouts.
+  - Storybook docs render `mermaid` fences as diagrams, with a diagram's `title` as a primary caption, `owned` and
+    `external` subgraphs as primary-tinted and grey-striped lanes, and GitHub alerts as Callouts.
+  - The Design System page opens with how views and components are designed in Claude Design, and shows the sync in one
+    diagram, split by who owns each step.
   - The development docs split Architecture, the decisions and their reasons, from Rules, the checkable rules with wrong and
     right examples. The release guide shows under Development, and the color system and release guides have flow diagrams.
   - Docs and skills are shorter, with examples and tables in place of repeated prose.
@@ -193,11 +196,10 @@ Spinner ignores `color`. Choose a baked variant:
     a softer border.
   - Storybook uses the ImFusion favicon set and starts on the next free port.
   - The production build omits the Vitest testing widget.
-  - Storybook runs on CSF Next with the experimental test syntax: a story's interaction tests are named `.test()` entries
-    under it in the sidebar and no longer autoplay when the story opens.
+  - The Storybook config is written with `defineMain` and `definePreview`.
 - Agent skills — Nikolaus Brunner <brunner@imfusion.com>
   - `imf-web-ui-update` reads the shipped `CHANGELOG.md` in its migration audit: it maps breaking changes and migration steps
-    to the project's call sites and lists fitting new features as suggestions.
+    to the project's call sites and lists fitting new features as suggestions, changing no file until the person approves.
   - `web-ui-dev-changelog` covers the mechanical log and the curated release section, and `web-ui-dev-release` curates
     the release notes through it.
   - `web-ui-dev-audit-docs` checks Mermaid diagrams against the skills and flows they draw.
@@ -236,7 +238,8 @@ Spinner ignores `color`. Choose a baked variant:
     differs from a convention as a deviation ([WEBSDK-218](https://imfusion.atlassian.net/browse/WEBSDK-218)).
   - The router sends broken-install and library-choice questions to the skill that answers them, and `imf-web-ui-setup`
     stays on the topic it was asked about.
-  - `imf-web-ui-ux` asks a question before recommending on a vague request.
+  - `imf-web-ui-ux` asks a question before recommending on a vague request and builds a fully specified one without asking.
+  - `imf-web-ui-components` starts every lookup at the component index, even for a component it already knows.
   - `imf-web-ui-update` stops on any uncommitted work before it installs or writes anything.
   - The `imf-web-ui-conventions` audit checklist lists only sections the React topic has ([WEBSDK-206](https://imfusion.atlassian.net/browse/WEBSDK-206)).
 - The format-on-edit agent hook runs Prettier from the edited file's own worktree, so a worktree's `.prettierignore` applies. — Nikolaus Brunner <brunner@imfusion.com>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@imfusion/web-ui",
-  "version": "0.6.4-dev.109.g8d507655",
+  "version": "0.6.4-dev.116.gbcea6d9a",
   "description": "The official Web UI component library for ImFusion web apps",
   "author": "ImFusion GmbH",
   "homepage": "https://imfusion.com",

package/src/llms/skills/imf-web-ui-components/SKILL.md

@@ -13,13 +13,14 @@ Use the generated package indexes. They are smaller and more reliable than readi
 
 ## Component lookup
 
-1. Read the identity index:
+1. Read the identity index first, even when you already know the component's name: it gives the docgen key and the status.
 
    ```sh
    cat node_modules/@imfusion/web-ui/src/llms/llms.gen.txt
    ```
 
-   It lists each component's name, category, status, purpose, and docgen entry.
+   It lists each component's name, category, status, purpose, and docgen entry. The docgen entry is the prop source; the
+   `.d.ts` files in `dist/` carry no defaults and hide upstream props behind their base types.
 
 2. Read only the matching entry from docgen:
 

package/src/llms/skills/imf-web-ui-update/SKILL.md

@@ -99,7 +99,8 @@ section after the pre-update version, up to and including the new one. Each sect
 `Breaking` entries are the release's own account of what changed. Then compare the old and new package metadata, current
 generated docs, types, and examples, and run the full verification again.
 
-Open the report with the releases read, then report separately:
+This phase reads and reports: every file stays as it is until the person approves the migration. Open the report with the
+releases read, then report separately:
 
 - migrations: every `Breaking` entry and migration step, mapped to the call sites it affects here and the fix the changelog
   shows; a step with no matching code is reported as not applicable;

package/src/llms/skills/imf-web-ui-ux/SKILL.md

@@ -25,7 +25,8 @@ no reason to reply. Ask one at a time, and stop once the choice is clear:
 4. What should users see when it is empty, loading, or failing?
 5. Is it a full page or part of another flow?
 
-If the prompt already answers a question, do not ask it again. Only when nobody is there to answer, or a question has gone
+A request that names the component, where it goes, and its initial state is specified: build it with no question. If the
+prompt already answers a question, do not ask it again. Only when nobody is there to answer, or a question has gone
 unanswered, make the conservative choice and state the assumption.
 
 ## Choose a surface