@modootoday/pmcp 0.13.1 → 0.14.0

package/plugins/react-dom-19/NOTICE

@@ -0,0 +1,51 @@
+pmcp
+
+Copyright (c) 2026 modootoday. All rights reserved.
+
+Licensor: modootoday
+Licensed under the Elastic License 2.0; see LICENSE.
+
+The licensor is modootoday, the company, not any individual contributor. This
+file names the licensor because the Elastic License 2.0 defines that term rather
+than carrying a copyright line of its own; LICENSE is kept unmodified.
+
+What the licence permits, in short, without replacing the terms in LICENSE:
+
+  - Using this software inside your own company, on any scale.
+  - Embedding it in a product you sell, and modifying or forking it.
+  - Redistributing it, with these notices intact.
+  - Running it locally as an MCP server, which is what it is for. A host
+    process spawning it on your own machine is use, not a hosted service.
+
+What it does not permit:
+
+  - Offering this software to third parties as a hosted or managed service.
+    A remotely hosted MCP endpoint serving other people is the case this
+    forbids.
+  - Circumventing licence key functionality.
+  - Removing or obscuring these notices.
+
+The Elastic License 2.0 is source-available, not an OSI-approved open source
+licence. It grants a patent licence and ends that licence if you assert a patent
+claim against the software; see the Patents section of LICENSE.
+
+LICENSE governs. Where this summary and LICENSE differ, LICENSE is what applies.
+
+---
+
+This software depends on the following packages, which are distributed under
+their own terms and are not covered by the licence above.
+
+  @modelcontextprotocol/server   MIT   Copyright (c) Anthropic, PBC
+  @modelcontextprotocol/core     MIT   Copyright (c) Anthropic, PBC
+  zod                            MIT   Copyright (c) Colin McDonnell
+  semver                         ISC   See the dependency's LICENSE file.
+  smol-toml              BSD-3-Clause   Copyright (c) Squirrel Chat et al.
+  yaml                           ISC   Copyright Eemeli Aro
+
+Full licence texts and copyright notices ship with those packages. Their
+respective licence terms govern distribution of those dependencies.
+
+@huggingface/transformers is an optional peer dependency. It is never
+distributed with this package; a user who wants semantic ranking installs it
+themselves, under its own Apache-2.0 terms.

package/plugins/react-dom-19/gemini-extension.json

@@ -0,0 +1 @@
+{ "name": "react-dom-19", "version": "19.0.1" }

package/plugins/react-dom-19/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "react-dom-19",
+  "version": "19.0.1",
+  "description": "Create and clean up roots, hydrate matching markup and verify form interaction.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/react-dom-19/skills/react-dom/SKILL.md

@@ -0,0 +1,178 @@
+---
+name: react-dom
+description: Use react-dom ^19.0.0 with React 19 root, server-rendering, portal, scheduling, form-status, and resource APIs. Avoid removed React 18-era entry points and distinguish browser-only APIs from standalone server APIs.
+---
+
+The two standalone server examples were verified against react-dom@19.2.8 on
+2026-09-07. Client lifecycle and hydration verification use the separate DOM
+fixture and must not be counted as DOM-free examples.
+
+# react-dom ^19.0.0
+
+## Scope
+
+`react-dom` is for web applications running in a browser DOM. It is not supported for React Native. The documented entry points include `react-dom`, `react-dom/client`, `react-dom/server`, and static APIs under `react-dom/static`.
+
+## React 19 root APIs
+
+Import client root APIs from `react-dom/client`, not from `react-dom`:
+
+```js
+import { createRoot } from 'react-dom/client';
+
+const root = createRoot(clientContainer);
+root.render(reactNode);
+```
+
+Use `createRoot` for client rendering and `hydrateRoot` when attaching React to existing server-rendered markup. Keep the returned root if the application needs to render again or unmount later.
+
+The hydration container already contains matching server HTML. Do not immediately render again or unmount while hydration is starting:
+
+```js
+import { hydrateRoot } from "react-dom/client";
+
+const hydratedRoot = hydrateRoot(serverContainer, matchingReactNode);
+```
+
+Keep react and react-dom on matching versions. Use a stable container owned by
+React, and call root.unmount() before an external owner removes that container.
+Create one root per independently managed React tree rather than a new root for
+every state update.
+
+```tsx
+import { createRoot } from "react-dom/client";
+import { App } from "./app";
+
+const container = document.getElementById("app");
+if (!container) throw new Error("Missing application container");
+const root = createRoot(container);
+root.render(<App />);
+
+export function dispose() {
+  root.unmount();
+}
+```
+
+hydrateRoot expects the initial client tree to match the server HTML. Resolve
+differences in data, locale, time, random values and invalid HTML nesting rather
+than routinely using suppressHydrationWarning. Browser-only content can render
+after an effect when that is the chosen product behavior. Capture recoverable
+hydration errors with onRecoverableError; successful recovery is still evidence
+of a mismatch. Avoid calling root.render before hydration finishes because it can
+discard the server HTML and switch the whole root to client rendering.
+
+### Common outdated shapes
+
+These React 18-era APIs were removed in React 19:
+
+- `render` — use `createRoot(domNode).render(reactNode)`.
+- `hydrate` — use `hydrateRoot(domNode, reactNode)`.
+- `unmountComponentAtNode` — use the root's `unmount()` method.
+- `findDOMNode`.
+- `renderToNodeStream`.
+- `renderToStaticNodeStream`.
+
+Do not import those removed APIs from `react-dom`.
+
+## Server rendering
+
+Import the documented server APIs from `react-dom/server`:
+
+```js
+import { renderToString, renderToStaticMarkup } from 'react-dom/server';
+
+renderToString(reactNode);
+renderToStaticMarkup(reactNode);
+```
+
+`renderToString` and `renderToStaticMarkup` can be used from a plain script without a browser DOM. The server entry point also documents `renderToReadableStream`, `resume`, `renderToPipeableStream`, and `resumeToPipeableStream`.
+
+```ts pmcp-example
+import assert from "node:assert/strict";
+import React from "react";
+import { renderToString } from "react-dom/server";
+
+const markup = renderToString(
+  React.createElement("main", null, React.createElement("h1", null, "Hello")),
+);
+
+assert.match(markup, /<main>/);
+assert.match(markup, /<h1>Hello<\/h1>/);
+```
+
+```ts pmcp-example
+import assert from "node:assert/strict";
+import React from "react";
+import { renderToStaticMarkup } from "react-dom/server";
+
+const markup = renderToStaticMarkup(
+  React.createElement("button", { type: "button" }, "Save"),
+);
+
+assert.equal(markup, '<button type="button">Save</button>');
+```
+
+## Browser APIs from `react-dom`
+
+The main entry point documents these APIs:
+
+```js
+import { createPortal, flushSync, preconnect } from 'react-dom';
+
+createPortal(children, domNode);
+flushSync(callback);
+preconnect(href);
+```
+
+Additional resource APIs are `prefetchDNS(href)`, `preload(href, options)`, `preloadModule(href, options?)`, `preinit(href, options?)`, and `preinitModule(href, options?)`.
+
+These APIs target the browser DOM or browser resource-loading behavior and cannot
+be exercised by the standalone server examples in this skill. A DOM simulator
+can check element behavior but cannot establish browser resource loading or
+layout. Frameworks may already handle resource loading, so the package APIs alone
+do not replace framework integration. Reserve flushSync for integration points
+that require a synchronous DOM update; it can force pending work and affect
+Suspense behavior.
+
+## Forms and React 19 additions
+
+`useFormStatus` is imported from `react-dom` and exposes form submission status such as `pending`:
+
+```jsx
+import { useFormStatus } from "react-dom";
+
+function DesignButton() {
+  const { pending } = useFormStatus();
+  return <button type="submit" disabled={pending} />;
+}
+```
+
+React 19 form actions can be supplied with the `action` prop:
+
+Pass the action function to `<form action={actionFunction}>` and render its fields inside that form.
+
+Successful Form Actions reset uncontrolled forms. `requestFormReset` performs a manual reset. These behaviors require the React/browser form runtime and are not demonstrated in a DOM-free script.
+
+## Features requiring tooling or framework integration
+
+- Server Actions using `"use server"` require a framework or build system to create server references and route requests. The directive is not a Server Component marker.
+- React Server Components bundler/framework implementation APIs do not follow semver; pin React or use a Canary release when implementing that infrastructure.
+- `use` cannot consume promises created during render. Promises must come from a Suspense-compatible library or framework.
+- `prerender` and `prerenderToNodeStream` wait for data and produce static output; they do not stream content as it loads.
+
+## Does not cover
+
+This skill does not cover framework-specific integration, Server Actions routing,
+Server Components bundler implementation, streaming server API usage or the
+react-dom/static API details. Verify browser rendering with the application's
+actual browser test environment; the fixture's DOM simulation checks roots,
+cleanup, form actions and matching-markup hydration without proving layout or
+framework behavior.
+
+## Sources
+
+- [React DOM APIs](https://react.dev/reference/react-dom)
+- [Client root lifecycle](https://react.dev/reference/react-dom/client/createRoot)
+- [Hydration requirements](https://react.dev/reference/react-dom/client/hydrateRoot)
+- [Resource hints](https://react.dev/reference/react-dom/preconnect)
+- [React 19 release](https://react.dev/blog/2024/12/05/react-19)

package/plugins/react-icons-5/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "react-icons-5",
+  "version": "5.0.0",
+  "description": "Use react-icons v5 icon-pack subpath imports, core component types, context, and documented packaging boundaries without relying on obsolete pre-v3 imports or unavailable manifest paths.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/react-icons-5/LICENSE

@@ -0,0 +1,93 @@
+Elastic License 2.0
+
+URL: https://www.elastic.co/licensing/elastic-license
+
+## Acceptance
+
+By using the software, you agree to all of the terms and conditions below.
+
+## Copyright License
+
+The licensor grants you a non-exclusive, royalty-free, worldwide,
+non-sublicensable, non-transferable license to use, copy, distribute, make
+available, and prepare derivative works of the software, in each case subject to
+the limitations and conditions below.
+
+## Limitations
+
+You may not provide the software to third parties as a hosted or managed
+service, where the service provides users with access to any substantial set of
+the features or functionality of the software.
+
+You may not move, change, disable, or circumvent the license key functionality
+in the software, and you may not remove or obscure any functionality in the
+software that is protected by the license key.
+
+You may not alter, remove, or obscure any licensing, copyright, or other notices
+of the licensor in the software. Any use of the licensor’s trademarks is subject
+to applicable law.
+
+## Patents
+
+The licensor grants you a license, under any patent claims the licensor can
+license, or becomes able to license, to make, have made, use, sell, offer for
+sale, import and have imported the software, in each case subject to the
+limitations and conditions in this license. This license does not cover any
+patent claims that you cause to be infringed by modifications or additions to
+the software. If you or your company make any written claim that the software
+infringes or contributes to infringement of any patent, your patent license for
+the software granted under these terms ends immediately. If your company makes
+such a claim, your patent license ends immediately for work on behalf of your
+company.
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of the software from you
+also gets a copy of these terms.
+
+If you modify the software, you must include in any modified copies of the
+software prominent notices stating that you have modified the software.
+
+## No Other Rights
+
+These terms do not imply any licenses other than those expressly granted in
+these terms.
+
+## Termination
+
+If you use the software in violation of these terms, such use is not licensed,
+and your licenses will automatically terminate. If the licensor provides you
+with a notice of your violation, and you cease all violation of this license no
+later than 30 days after you receive that notice, your licenses will be
+reinstated retroactively. However, if you violate these terms after such
+reinstatement, any additional violation of these terms will cause your licenses
+to terminate automatically and permanently.
+
+## No Liability
+
+*As far as the law allows, the software comes as is, without any warranty or
+condition, and the licensor will not be liable to you for any damages arising
+out of these terms or the use or nature of the software, under any kind of
+legal claim.*
+
+## Definitions
+
+The **licensor** is the entity offering these terms, and the **software** is the
+software the licensor makes available under these terms, including any portion
+of it.
+
+**you** refers to the individual or entity agreeing to these terms.
+
+**your company** is any legal entity, sole proprietorship, or other kind of
+organization that you work for, plus all organizations that have control over,
+are under the control of, or are under common control with that
+organization. **control** means ownership of substantially all the assets of an
+entity, or the power to direct its management and policies by vote, contract, or
+otherwise. Control can be direct or indirect.
+
+**your licenses** are all the licenses granted to you for the software under
+these terms.
+
+**use** means anything you do with the software requiring one of your licenses.
+
+**trademark** means trademarks, service marks, and similar rights.

package/plugins/react-icons-5/NOTICE

@@ -0,0 +1,51 @@
+pmcp
+
+Copyright (c) 2026 modootoday. All rights reserved.
+
+Licensor: modootoday
+Licensed under the Elastic License 2.0; see LICENSE.
+
+The licensor is modootoday, the company, not any individual contributor. This
+file names the licensor because the Elastic License 2.0 defines that term rather
+than carrying a copyright line of its own; LICENSE is kept unmodified.
+
+What the licence permits, in short, without replacing the terms in LICENSE:
+
+  - Using this software inside your own company, on any scale.
+  - Embedding it in a product you sell, and modifying or forking it.
+  - Redistributing it, with these notices intact.
+  - Running it locally as an MCP server, which is what it is for. A host
+    process spawning it on your own machine is use, not a hosted service.
+
+What it does not permit:
+
+  - Offering this software to third parties as a hosted or managed service.
+    A remotely hosted MCP endpoint serving other people is the case this
+    forbids.
+  - Circumventing licence key functionality.
+  - Removing or obscuring these notices.
+
+The Elastic License 2.0 is source-available, not an OSI-approved open source
+licence. It grants a patent licence and ends that licence if you assert a patent
+claim against the software; see the Patents section of LICENSE.
+
+LICENSE governs. Where this summary and LICENSE differ, LICENSE is what applies.
+
+---
+
+This software depends on the following packages, which are distributed under
+their own terms and are not covered by the licence above.
+
+  @modelcontextprotocol/server   MIT   Copyright (c) Anthropic, PBC
+  @modelcontextprotocol/core     MIT   Copyright (c) Anthropic, PBC
+  zod                            MIT   Copyright (c) Colin McDonnell
+  semver                         ISC   See the dependency's LICENSE file.
+  smol-toml              BSD-3-Clause   Copyright (c) Squirrel Chat et al.
+  yaml                           ISC   Copyright Eemeli Aro
+
+Full licence texts and copyright notices ship with those packages. Their
+respective licence terms govern distribution of those dependencies.
+
+@huggingface/transformers is an optional peer dependency. It is never
+distributed with this package; a user who wants semantic ranking installs it
+themselves, under its own Apache-2.0 terms.

package/plugins/react-icons-5/gemini-extension.json

@@ -0,0 +1 @@
+{ "name": "react-icons-5", "version": "5.0.0" }

package/plugins/react-icons-5/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "react-icons-5",
+  "version": "5.0.0",
+  "description": "Use react-icons v5 icon-pack subpath imports, core component types, context, and documented packaging boundaries without relying on obsolete pre-v3 imports or unavailable manifest paths.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/react-icons-5/skills/react-icons/SKILL.md

@@ -0,0 +1,194 @@
+---
+name: react-icons
+description: Use react-icons v5 icon-pack subpath imports, core component types, context, and documented packaging boundaries without relying on obsolete pre-v3 imports or unavailable manifest paths.
+---
+
+Verified against react-icons@5.7.0 on 2026-09-07. 3 of 3 examples executed.
+
+# react-icons
+
+## Version and package boundary
+
+This skill targets `react-icons` `^5.0.0`, which stays within major version 5. The researched documented release is 5.7.0. React is a peer dependency, and the package publishes CommonJS, ES module, and TypeScript entry points. It declares `sideEffects: false`.
+
+The icons are React components. Normal usage belongs in a React application or another React renderer. The standalone examples below create React elements and inspect the exported API; they do not attempt to render into a browser or server output.
+
+## Import icons from an icon-pack subpath
+
+Use a named import from the pack subpath:
+
+```tsx
+import { FaBeer } from "react-icons/fa";
+```
+
+The same pattern applies to other packs, for example:
+
+```tsx
+import { ICON_NAME } from "react-icons/md";
+```
+
+The documented pack subpaths include `ai`, `bi`, `bs`, `cg`, `ci`, `di`, `fa`, `fa6`, `fc`, `fi`, `gi`, `go`, `gr`, `hi`, `hi2`, `im`, `io`, `io5`, `lia`, `lu`, `md`, `pi`, `ri`, `rx`, `si`, `sl`, `tb`, `tfi`, `ti`, `vsc`, and `wi`.
+
+A typical React usage is:
+
+```tsx
+import { FaBeer } from "react-icons/fa";
+
+function Question() {
+  return <h3>Lets go for a <FaBeer />?</h3>;
+}
+```
+
+### Common import mistake
+
+Do not use the old pre-v3 per-file form:
+
+```tsx
+import FaBeer from "react-icons/lib/fa/beer";
+```
+
+That shape was replaced by the named per-pack import:
+
+```tsx
+import { FaBeer } from "react-icons/fa";
+```
+
+The v4-shaped named subpath imports remain the documented v5 shape. The v5.0.0 release specifically documents strict ESM loader compatibility rather than a new icon import migration.
+
+### Standalone import check
+
+```ts pmcp-example
+import assert from "node:assert/strict";
+import { createElement } from "react";
+import { FaBeer } from "react-icons/fa";
+
+assert.equal(typeof FaBeer, "function");
+
+const element = createElement(FaBeer, { title: "Beer" });
+assert.equal(element.type, FaBeer);
+assert.equal(element.props.title, "Beer");
+```
+
+## Core component API
+
+The core API exposes these types and functions:
+
+- `IconTree`: `{ tag, attr, child }` tree data for an icon.
+- `GenIcon(data)`: creates an icon component from an `IconTree`.
+- `IconBase`: the base SVG component.
+- `IconType`: a component accepting `IconBaseProps`.
+- `IconBaseProps`: React SVG attributes plus optional `children`, `size`, `color`, and `title`.
+
+The core exports are available from `react-icons` and `react-icons/lib` according to the package declarations. `GenIcon` is useful when icon tree data is available programmatically; normal consumers should generally import generated icons from their pack subpath.
+
+`size` accepts a string or number. `color` and `title` are also supported alongside normal React SVG attributes.
+
+```ts pmcp-example
+import assert from "node:assert/strict";
+import { createElement } from "react";
+import { GenIcon } from "react-icons";
+
+const Icon = GenIcon({
+  tag: "path",
+  attr: { d: "M0 0h10v10H0z" },
+  child: [],
+});
+
+assert.equal(typeof Icon, "function");
+const element = createElement(Icon, { size: 24, color: "blue", title: "Square" });
+assert.equal(element.type, Icon);
+assert.equal(element.props.size, 24);
+assert.equal(element.props.color, "blue");
+assert.equal(element.props.title, "Square");
+```
+
+## Global icon context
+
+Import `IconContext` and provide values around icons in a React tree:
+
+```tsx
+import { IconContext } from "react-icons";
+
+<IconContext.Provider value={{ color: "blue", className: "global-class-name" }}>
+  <div><FaFolder /></div>
+</IconContext.Provider>
+```
+
+The context value can contain:
+
+- `color?: string`
+- `size?: string`
+- `className?: string`
+- `style?: React.CSSProperties`
+- `attr?: React.SVGAttributes<SVGElement>`
+
+`DefaultContext` is also exported. The context is a React context object, so provide it through React rather than treating it as a standalone plain-object configuration API.
+
+```ts pmcp-example
+import assert from "node:assert/strict";
+import { createElement } from "react";
+import { DefaultContext, IconContext } from "react-icons";
+
+assert.equal(typeof IconContext.Provider, "object");
+assert.equal(typeof DefaultContext, "object");
+
+const child = createElement("span", null, "icon");
+const provider = createElement(
+  IconContext.Provider,
+  { value: { color: "blue", className: "global-class-name" } },
+  child,
+);
+
+assert.equal(provider.type, IconContext.Provider);
+assert.equal(provider.props.value.color, "blue");
+assert.equal(provider.props.value.className, "global-class-name");
+```
+
+## Manifest declarations and runtime path
+
+The research describes an `IconManifestType` with these fields:
+
+```ts
+interface IconManifestType {
+  id: string;
+  name: string;
+  projectUrl: string;
+  license: string;
+  licenseUrl: string;
+}
+```
+
+It also documents an `IconsManifest` declaration. However, the documented declaration path `react-icons/lib/iconsManifest` is not a runnable runtime module in the tested `react-icons@5.7.0` installation. Do not make application code depend on that path without verifying the installed package exposes it. Manifest inspection is therefore not covered by a standalone example here.
+
+## Installation and packaging notes
+
+The standard installation is:
+
+```sh
+npm install react-icons --save
+```
+
+or:
+
+```sh
+yarn add react-icons
+```
+
+There is also an `@react-icons/all-files` package with imports such as:
+
+```tsx
+import { FaBeer } from "@react-icons/all-files/fa/FaBeer";
+```
+
+The researched documentation describes it as a separate, slower-to-install option for environments such as Meteor or Gatsby and warns that it has not had a new release for some time. Prefer the standard `react-icons` package unless that separate packaging mode is specifically required.
+
+## What this skill does not cover
+
+- Rendering icons in a browser, server-rendering, or framework-specific integration.
+- The behavior of every individual icon or icon-pack export.
+- Choosing an icon by visual appearance or searching the manifest.
+- Using `IconsManifest` at a runtime path not present in the tested installation.
+- The internal SVG rendering details of `IconBase`.
+- Building or modifying the icon database and repository development commands.
+- The `@react-icons/all-files` package beyond its documented import shape.
+- Any API or behavior not shown in the supplied v5 research.

package/plugins/react-is-19/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "react-is-19",
+  "version": "19.0.0",
+  "description": "Use react-is 19 to identify React element brands and validate component types. Covers the React 19 export surface, the removal of React 18 async/concurrent aliases, and standalone checks that run without JSX, React, a DOM, or a test runner.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}