@imfusion/web-ui 0.5.1-dev.6.gec5b9f17 → 0.5.1-dev.6.gece7a7b5

package/README.md

@@ -2,11 +2,6 @@
 
 `@imfusion/web-ui` — the official shared Web UI library for ImFusion web apps, built on Base UI.
 
-- [Usage](#usage) — install, wire up, and keep the version current
-- [Documentation](#documentation) — Storybook and the developer docs
-- [Development](#development) — working on the library itself, including the Agent Skills
-- [Releasing](#releasing) — how versions are derived and how to cut one
-
 ## Usage
 
 The packages are private on npmjs.com.
@@ -38,30 +33,8 @@ import "@imfusion/web-ui/styles.css";
 import { WebUIProvider } from "@imfusion/web-ui";
 ```
 
-### LLM integration
-
-The `web-ui` package does offer first-class support for LLMs, but it's not wired up by default.
-
-To install the skills, run this command after the package is installed:
-
-```bash
-npx web-ui-install-skills
-```
-
-The binary will ask you which LLM client you want to use and install everything it needs.
-
-**Available consumer skills - `/imf-web-ui-*`**
-
-| Skill                                 | What it does                                                                         |
-| ------------------------------------- | ------------------------------------------------------------------------------------ |
-| `/imf-web-ui`                         | The router: decides whether guidance is needed, then which companion to open.        |
-| `/imf-web-ui-setup`                   | One-time wiring in a consumer project — the styles import and the provider.          |
-| `/imf-web-ui-components`              | Component reference — what exists and how it's meant to be used.                     |
-| `/imf-web-ui-ux`                      | UX guidance for building interfaces with the library.                                |
-| `/imf-web-ui-frontend-patterns`       | Frontend patterns, including the sanctioned styling seams (tokens, data attributes). |
-| `/imf-web-ui-imfusion-frontend-setup` | Set up or audit an ImFusion frontend's tooling against the house baseline.           |
-
-Start at `/imf-web-ui` — it routes to the rest. Storybook's **User Guide → AI Agents** page covers the whole family.
+**There is also an AI skill to help you set up the Web UI library in your project:
+[`/imf-web-ui-setup`](./src/llms/skills/imf-web-ui-setup/SKILL.md). **
 
 ### Versions and updates
 
@@ -85,6 +58,20 @@ Every merge to master publishes a new build under the `dev` dist-tag. Which spec
 - **A `file:` tarball never updates.** npm copies the archive into `node_modules` and re-copies the same one on every
   install. Switch to `dev` or a version range to get updates.
 
+### Consumer skills — `imf-web-ui-*`
+
+These skills are shipped with a `imf-web-ui` prefix, so to make their names identifiable and not pollute the skill namespace
+of the user.
+
+| Skill                                 | What it does                                                                         |
+| ------------------------------------- | ------------------------------------------------------------------------------------ |
+| `/imf-web-ui`                         | The router: decides whether guidance is needed, then which companion to open.        |
+| `/imf-web-ui-setup`                   | One-time wiring in a consumer project — the styles import and the provider.          |
+| `/imf-web-ui-components`              | Component reference — what exists and how it's meant to be used.                     |
+| `/imf-web-ui-ux`                      | UX guidance for building interfaces with the library.                                |
+| `/imf-web-ui-frontend-patterns`       | Frontend patterns, including the sanctioned styling seams (tokens, data attributes). |
+| `/imf-web-ui-imfusion-frontend-setup` | Set up or audit an ImFusion frontend's tooling against the house baseline.           |
+
 ## Documentation
 
 **[Storybook](https://storybook.js.org/)** is the documentation platform — the component catalog, every prop, and the setup
@@ -107,10 +94,9 @@ npm run git:config   # hooks path + rebase-only pull/merge
 
 **Try out **`/web-ui-dev-getting-started`** for an ai assisted start.**
 
-### LLM integration
+### Development skills — `web-ui-dev-*`
 
-These skills are shipped with a `/web-ui-dev-*` prefix, so to make their names identifiable and not pollute the skill
-namespace.
+These skills are shipped with a `web-ui-dev` prefix, so to make their names identifiable and not pollute the skill namespace.
 
 | Skill                                     | What it does                                                                          |
 | ----------------------------------------- | ------------------------------------------------------------------------------------- |
@@ -145,18 +131,8 @@ Given the tag `web-ui/v0.5.0`:
 | Exactly on `web-ui/v0.5.0` | `0.5.0`                 | `latest` |
 | 5 commits after that tag   | `0.5.1-dev.5.gb4de52d7` | `dev`    |
 
-The off-tag string breaks down as:
-
-```
-0.5.1-dev.5.gb4de52d7
-└─┬─┘ └┬┘ │ └───┬────┘
-  │    │  │     └── commit hash, abbreviated; the leading g means "git"
-  │    │  └──────── commits since the tag
-  │    └─────────── pre-release marker, which is what puts it on the dev tag
-  └──────────────── the tag's version, patch bumped
-```
-
-Bumping the patch is what makes a dev build sort above the release it follows and below the next one.
+where `5` is the number of commits since the tag and `b4de52d7` the abbreviated hash. Off-tag builds bump the patch, so a dev
+build always sorts above the release it follows and below the next one.
 
 Every build of `master` publishes a `dev` version automatically. To check what the current checkout would publish:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@imfusion/web-ui",
-  "version": "0.5.1-dev.6.gec5b9f17",
+  "version": "0.5.1-dev.6.gece7a7b5",
   "description": "The official Web UI component library for ImFusion web apps",
   "author": "ImFusion GmbH",
   "license": "UNLICENSED",