@machfivetechchicago/machvive-webmcp-ai 5.7.0 → 5.7.2

package/README.md

@@ -11,6 +11,7 @@
   <a href="LICENSE"><img alt="license" src="https://img.shields.io/npm/l/@machfivetechchicago/machvive-webmcp-ai.svg"></a>
   <img alt="types" src="https://img.shields.io/badge/types-included-blue.svg">
   <img alt="dependencies" src="https://img.shields.io/badge/dependencies-0-brightgreen.svg">
+  <a href="https://github.com/Mach-Five-Group/machvive-webmcp-ai/wiki/Machvive-WebMCP-Polyfill-Web-Component-Lib"><img alt="docs" src="https://img.shields.io/badge/docs-wiki-blue.svg"></a>
 </p>
 
 WebMCP empowers agents by giving them access to your core business functionality within a safe, semantic sandbox.
@@ -29,6 +30,10 @@ elements with Shadow DOM that work anywhere `customElements` does.
 | WebMCP analytics | `<machvive-webmcp-analytics>` | Captures every tool call for listing, editing, export, replay, and dataLayer |
 | Lorum Ipsum | `<machvive-lorum-ipsum>` | Placeholder copy that projects slotted content |
 
+📖 **[Read the full guide on the Wiki](https://github.com/Mach-Five-Group/machvive-webmcp-ai/wiki/Machvive-WebMCP-Polyfill-Web-Component-Lib)** — what WebMCP is and why it beats
+scripted clicking, how the components compose, and the constraints worth knowing
+before you adopt.
+
 <img width="1098" height="894" alt="m5t_machvive_ai_webmcp" src="https://github.com/user-attachments/assets/a1433ff0-f8a9-46fb-ad59-735aed155ff8" />
 
 ## ⚡ Integration with Vite (Vanilla JS)
@@ -254,6 +259,22 @@ themes unless you scope your override inside your own media query.
 Every combination of OS preference and `theme` is verified to meet WCAG AA
 (≥ 4.5:1) across the full UI. If you override tokens, re-check your own contrast.
 
+## 🤖 Claude Code skill
+
+If you build with [Claude Code](https://claude.com/claude-code), install the
+companion skill so Claude knows how to use these components — the API, and the
+constraints that quietly break integrations:
+
+```
+/plugin marketplace add Mach-Five-Group/machvive-webmcp-ai
+/plugin install machvive-webmcp@machvive
+```
+
+Claude then knows to import analytics before registering tools, that the polyfill
+needs a secure context, that a top-level import breaks under SSR, and that
+`sideEffects: false` silently drops the component registrations — the four things
+that fail in ways that look like something else.
+
 ## TypeScript
 
 Declarations ship with the package — no `@types/*` needed. Importing a component
@@ -313,6 +334,11 @@ A static top-level `import` will not work in any of these: the module is evaluat
 during the server render, before any browser-only lifecycle hook gets a chance to run.
 Use the dynamic `import()` form shown above.
 
+## Documentation
+
+Full guide, architecture notes, and adoption constraints live on the
+**[project Wiki](https://github.com/Mach-Five-Group/machvive-webmcp-ai/wiki)**.
+
 ## License
 
 [Apache-2.0](LICENSE) © MachFiveTech Chicago

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@machfivetechchicago/machvive-webmcp-ai",
-  "version": "5.7.0",
+  "version": "5.7.2",
   "description": "I don't want to use your product's agent; I want my agent to be able to use your product.",
   "keywords": [
     "WebMCP",
@@ -66,5 +66,8 @@
   "devDependencies": {
     "fake-indexeddb": "^6.2.5",
     "jsdom": "^29.1.1"
+  },
+  "dependencies": {
+    "@machfivetechchicago/machvive-webmcp-ai": "^5.7.1"
   }
 }