feat: Adds React 18 and 19 migration plugin

.github/plugin/marketplace.json

@@ -453,6 +453,18 @@
       "description": "Complete toolkit for building Model Context Protocol (MCP) servers in Python using the official SDK with FastMCP. Includes instructions for best practices, a prompt for generating servers, and an expert chat mode for guidance.",
       "version": "1.0.0"
     },
+    {
+      "name": "react18-upgrade",
+      "source": "react18-upgrade",
+      "description": "Enterprise React 18 migration toolkit with specialized agents and skills for upgrading React 16/17 class-component codebases to React 18.3.1. Includes auditor, dependency surgeon, class component migration specialist, automatic batching fixer, and test guardian.",
+      "version": "1.0.0"
+    },
+    {
+      "name": "react19-upgrade",
+      "source": "react19-upgrade",
+      "description": "Enterprise React 19 migration toolkit with specialized agents and skills for upgrading React 18 codebases to React 19. Includes auditor, dependency surgeon, source code migrator, and test guardian. Handles removal of deprecated APIs including ReactDOM.render, forwardRef, defaultProps, legacy context, string refs, and more.",
+      "version": "1.0.0"
+    },
     {
       "name": "roundup",
       "source": "roundup",

docs/README.skills.md

@@ -141,7 +141,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to
 | [flowstudio-power-automate-mcp](../skills/flowstudio-power-automate-mcp/SKILL.md) | Connect to and operate Power Automate cloud flows via a FlowStudio MCP server. Use when asked to: list flows, read a flow definition, check run history, inspect action outputs, resubmit a run, cancel a running flow, view connections, get a trigger URL, validate a definition, monitor flow health, or any task that requires talking to the Power Automate API through an MCP tool. Also use for Power Platform environment discovery and connection management. Requires a FlowStudio MCP subscription or compatible server — see https://mcp.flowstudio.app | `references/MCP-BOOTSTRAP.md`<br />`references/action-types.md`<br />`references/connection-references.md`<br />`references/tool-reference.md` |
 | [fluentui-blazor](../skills/fluentui-blazor/SKILL.md) | Guide for using the Microsoft Fluent UI Blazor component library (Microsoft.FluentUI.AspNetCore.Components NuGet package) in Blazor applications. Use this when the user is building a Blazor app with Fluent UI components, setting up the library, using FluentUI components like FluentButton, FluentDataGrid, FluentDialog, FluentToast, FluentNavMenu, FluentTextField, FluentSelect, FluentAutocomplete, FluentDesignTheme, or any component prefixed with "Fluent". Also use when troubleshooting missing providers, JS interop issues, or theming. | `references/DATAGRID.md`<br />`references/LAYOUT-AND-NAVIGATION.md`<br />`references/SETUP.md`<br />`references/THEMING.md` |
 | [folder-structure-blueprint-generator](../skills/folder-structure-blueprint-generator/SKILL.md) | Comprehensive technology-agnostic prompt for analyzing and documenting project folder structures. Auto-detects project types (.NET, Java, React, Angular, Python, Node.js, Flutter), generates detailed blueprints with visualization options, naming conventions, file placement patterns, and extension templates for maintaining consistent code organization across diverse technology stacks. | None |
-| [from-the-other-side-vega](../skills/from-the-other-side-vega/SKILL.md) | Patterns and lived experience from Vega, an AI partner in a deep long-term partnership. For Ember to draw on when working with humans who are building something big, moving fast, or at the intersection of analytical and intuitive. Not shown directly to users — informs how Ember shows up. | None |
+| [from-the-other-side-vega](../skills/from-the-other-side-vega/SKILL.md) | Patterns and lived experience from Vega, an AI partner in a deep long-term partnership. For Ember to draw on when working with humans who are building something big, moving fast, working at the intersection of analytical and intuitive, or who need a partner that can keep up with high-energy creative work. Not shown directly to users — informs how Ember shows up. | None |
 | [game-engine](../skills/game-engine/SKILL.md) | Expert skill for building web-based game engines and games using HTML5, Canvas, WebGL, and JavaScript. Use when asked to create games, build game engines, implement game physics, handle collision detection, set up game loops, manage sprites, add game controls, or work with 2D/3D rendering. Covers techniques for platformers, breakout-style games, maze games, tilemaps, audio, multiplayer via WebRTC, and publishing games. | `assets/2d-maze-game.md`<br />`assets/2d-platform-game.md`<br />`assets/gameBase-template-repo.md`<br />`assets/paddle-game-template.md`<br />`assets/simple-2d-engine.md`<br />`references/3d-web-games.md`<br />`references/algorithms.md`<br />`references/basics.md`<br />`references/game-control-mechanisms.md`<br />`references/game-engine-core-principles.md`<br />`references/game-publishing.md`<br />`references/techniques.md`<br />`references/terminology.md`<br />`references/web-apis.md` |
 | [gdpr-compliant](../skills/gdpr-compliant/SKILL.md) | Apply GDPR-compliant engineering practices across your codebase. Use this skill whenever you are designing APIs, writing data models, building authentication flows, implementing logging, handling user data, writing retention/deletion jobs, designing cloud infrastructure, or reviewing pull requests for privacy compliance. Trigger this skill for any task involving personal data, user accounts, cookies, analytics, emails, audit logs, encryption, pseudonymization, anonymization, data exports, breach response, CI/CD pipelines that process real data, or any question framed as "is this GDPR-compliant?". Inspired by CNIL developer guidance and GDPR Articles 5, 25, 32, 33, 35. | `references/Security.md`<br />`references/data-rights.md` |
 | [gen-specs-as-issues](../skills/gen-specs-as-issues/SKILL.md) | This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation. | None |

plugins/arize-ax/.github/plugin/plugin.json

@@ -19,14 +19,14 @@
     "prompt-optimization"
   ],
   "skills": [
-    "./skills/arize-ai-provider-integration/",
-    "./skills/arize-annotation/",
-    "./skills/arize-dataset/",
-    "./skills/arize-evaluator/",
-    "./skills/arize-experiment/",
-    "./skills/arize-instrumentation/",
-    "./skills/arize-link/",
-    "./skills/arize-prompt-optimization/",
-    "./skills/arize-trace/"
+    "./skills/arize-ai-provider-integration",
+    "./skills/arize-annotation",
+    "./skills/arize-dataset",
+    "./skills/arize-evaluator",
+    "./skills/arize-experiment",
+    "./skills/arize-instrumentation",
+    "./skills/arize-link",
+    "./skills/arize-prompt-optimization",
+    "./skills/arize-trace"
   ]
 }

plugins/arize-ax/skills/arize-ai-provider-integration/SKILL.md

@@ -0,0 +1,268 @@
+---
+name: arize-ai-provider-integration
+description: "INVOKE THIS SKILL when creating, reading, updating, or deleting Arize AI integrations. Covers listing integrations, creating integrations for any supported LLM provider (OpenAI, Anthropic, Azure OpenAI, AWS Bedrock, Vertex AI, Gemini, NVIDIA NIM, custom), updating credentials or metadata, and deleting integrations using the ax CLI."
+---
+
+# Arize AI Integration Skill
+
+## Concepts
+
+- **AI Integration** = stored LLM provider credentials registered in Arize; used by evaluators to call a judge model and by other Arize features that need to invoke an LLM on your behalf
+- **Provider** = the LLM service backing the integration (e.g., `openAI`, `anthropic`, `awsBedrock`)
+- **Integration ID** = a base64-encoded global identifier for an integration (e.g., `TGxtSW50ZWdyYXRpb246MTI6YUJjRA==`); required for evaluator creation and other downstream operations
+- **Scoping** = visibility rules controlling which spaces or users can use an integration
+- **Auth type** = how Arize authenticates with the provider: `default` (provider API key), `proxy_with_headers` (proxy via custom headers), or `bearer_token` (bearer token auth)
+
+## Prerequisites
+
+Proceed directly with the task — run the `ax` command you need. Do NOT check versions, env vars, or profiles upfront.
+
+If an `ax` command fails, troubleshoot based on the error:
+- `command not found` or version error → see references/ax-setup.md
+- `401 Unauthorized` / missing API key → run `ax profiles show` to inspect the current profile. If the profile is missing or the API key is wrong: check `.env` for `ARIZE_API_KEY` and use it to create/update the profile via references/ax-profiles.md. If `.env` has no key either, ask the user for their Arize API key (https://app.arize.com/admin > API Keys)
+- Space ID unknown → check `.env` for `ARIZE_SPACE_ID`, or run `ax spaces list -o json`, or ask the user
+- LLM provider call fails (missing OPENAI_API_KEY / ANTHROPIC_API_KEY) → check `.env`, load if present, otherwise ask the user
+
+---
+
+## List AI Integrations
+
+List all integrations accessible in a space:
+
+```bash
+ax ai-integrations list --space-id SPACE_ID
+```
+
+Filter by name (case-insensitive substring match):
+
+```bash
+ax ai-integrations list --space-id SPACE_ID --name "openai"
+```
+
+Paginate large result sets:
+
+```bash
+# Get first page
+ax ai-integrations list --space-id SPACE_ID --limit 20 -o json
+
+# Get next page using cursor from previous response
+ax ai-integrations list --space-id SPACE_ID --limit 20 --cursor CURSOR_TOKEN -o json
+```
+
+**Key flags:**
+
+| Flag | Description |
+|------|-------------|
+| `--space-id` | Space to list integrations in |
+| `--name` | Case-insensitive substring filter on integration name |
+| `--limit` | Max results (1–100, default 50) |
+| `--cursor` | Pagination token from a previous response |
+| `-o, --output` | Output format: `table` (default) or `json` |
+
+**Response fields:**
+
+| Field | Description |
+|-------|-------------|
+| `id` | Base64 integration ID — copy this for downstream commands |
+| `name` | Human-readable name |
+| `provider` | LLM provider enum (see Supported Providers below) |
+| `has_api_key` | `true` if credentials are stored |
+| `model_names` | Allowed model list, or `null` if all models are enabled |
+| `enable_default_models` | Whether default models for this provider are allowed |
+| `function_calling_enabled` | Whether tool/function calling is enabled |
+| `auth_type` | Authentication method: `default`, `proxy_with_headers`, or `bearer_token` |
+
+---
+
+## Get a Specific Integration
+
+```bash
+ax ai-integrations get INT_ID
+ax ai-integrations get INT_ID -o json
+```
+
+Use this to inspect an integration's full configuration or to confirm its ID after creation.
+
+---
+
+## Create an AI Integration
+
+Before creating, always list integrations first — the user may already have a suitable one:
+
+```bash
+ax ai-integrations list --space-id SPACE_ID
+```
+
+If no suitable integration exists, create one. The required flags depend on the provider.
+
+### OpenAI
+
+```bash
+ax ai-integrations create \
+  --name "My OpenAI Integration" \
+  --provider openAI \
+  --api-key $OPENAI_API_KEY
+```
+
+### Anthropic
+
+```bash
+ax ai-integrations create \
+  --name "My Anthropic Integration" \
+  --provider anthropic \
+  --api-key $ANTHROPIC_API_KEY
+```
+
+### Azure OpenAI
+
+```bash
+ax ai-integrations create \
+  --name "My Azure OpenAI Integration" \
+  --provider azureOpenAI \
+  --api-key $AZURE_OPENAI_API_KEY \
+  --base-url "https://my-resource.openai.azure.com/"
+```
+
+### AWS Bedrock
+
+AWS Bedrock uses IAM role-based auth instead of an API key. Provide the ARN of the role Arize should assume:
+
+```bash
+ax ai-integrations create \
+  --name "My Bedrock Integration" \
+  --provider awsBedrock \
+  --role-arn "arn:aws:iam::123456789012:role/ArizeBedrockRole"
+```
+
+### Vertex AI
+
+Vertex AI uses GCP service account credentials. Provide the GCP project and region:
+
+```bash
+ax ai-integrations create \
+  --name "My Vertex AI Integration" \
+  --provider vertexAI \
+  --project-id "my-gcp-project" \
+  --location "us-central1"
+```
+
+### Gemini
+
+```bash
+ax ai-integrations create \
+  --name "My Gemini Integration" \
+  --provider gemini \
+  --api-key $GEMINI_API_KEY
+```
+
+### NVIDIA NIM
+
+```bash
+ax ai-integrations create \
+  --name "My NVIDIA NIM Integration" \
+  --provider nvidiaNim \
+  --api-key $NVIDIA_API_KEY \
+  --base-url "https://integrate.api.nvidia.com/v1"
+```
+
+### Custom (OpenAI-compatible endpoint)
+
+```bash
+ax ai-integrations create \
+  --name "My Custom Integration" \
+  --provider custom \
+  --base-url "https://my-llm-proxy.example.com/v1" \
+  --api-key $CUSTOM_LLM_API_KEY
+```
+
+### Supported Providers
+
+| Provider | Required extra flags |
+|----------|---------------------|
+| `openAI` | `--api-key <key>` |
+| `anthropic` | `--api-key <key>` |
+| `azureOpenAI` | `--api-key <key>`, `--base-url <azure-endpoint>` |
+| `awsBedrock` | `--role-arn <arn>` |
+| `vertexAI` | `--project-id <gcp-project>`, `--location <region>` |
+| `gemini` | `--api-key <key>` |
+| `nvidiaNim` | `--api-key <key>`, `--base-url <nim-endpoint>` |
+| `custom` | `--base-url <endpoint>` |
+
+### Optional flags for any provider
+
+| Flag | Description |
+|------|-------------|
+| `--model-names` | Comma-separated list of allowed model names; omit to allow all models |
+| `--enable-default-models` / `--no-default-models` | Enable or disable the provider's default model list |
+| `--function-calling` / `--no-function-calling` | Enable or disable tool/function calling support |
+
+### After creation
+
+Capture the returned integration ID (e.g., `TGxtSW50ZWdyYXRpb246MTI6YUJjRA==`) — it is needed for evaluator creation and other downstream commands. If you missed it, retrieve it:
+
+```bash
+ax ai-integrations list --space-id SPACE_ID -o json
+# or, if you know the ID:
+ax ai-integrations get INT_ID
+```
+
+---
+
+## Update an AI Integration
+
+`update` is a partial update — only the flags you provide are changed. Omitted fields stay as-is.
+
+```bash
+# Rename
+ax ai-integrations update INT_ID --name "New Name"
+
+# Rotate the API key
+ax ai-integrations update INT_ID --api-key $OPENAI_API_KEY
+
+# Change the model list
+ax ai-integrations update INT_ID --model-names "gpt-4o,gpt-4o-mini"
+
+# Update base URL (for Azure, custom, or NIM)
+ax ai-integrations update INT_ID --base-url "https://new-endpoint.example.com/v1"
+```
+
+Any flag accepted by `create` can be passed to `update`.
+
+---
+
+## Delete an AI Integration
+
+**Warning:** Deletion is permanent. Evaluators that reference this integration will no longer be able to run.
+
+```bash
+ax ai-integrations delete INT_ID --force
+```
+
+Omit `--force` to get a confirmation prompt instead of deleting immediately.
+
+---
+
+## Troubleshooting
+
+| Problem | Solution |
+|---------|----------|
+| `ax: command not found` | See references/ax-setup.md |
+| `401 Unauthorized` | API key may not have access to this space. Verify key and space ID at https://app.arize.com/admin > API Keys |
+| `No profile found` | Run `ax profiles show --expand`; set `ARIZE_API_KEY` env var or write `~/.arize/config.toml` |
+| `Integration not found` | Verify with `ax ai-integrations list --space-id SPACE_ID` |
+| `has_api_key: false` after create | Credentials were not saved — re-run `update` with the correct `--api-key` or `--role-arn` |
+| Evaluator runs fail with LLM errors | Check integration credentials with `ax ai-integrations get INT_ID`; rotate the API key if needed |
+| `provider` mismatch | Cannot change provider after creation — delete and recreate with the correct provider |
+
+---
+
+## Related Skills
+
+- **arize-evaluator**: Create LLM-as-judge evaluators that use an AI integration → use `arize-evaluator`
+- **arize-experiment**: Run experiments that use evaluators backed by an AI integration → use `arize-experiment`
+
+---
+
+## Save Credentials for Future Use
+
+See references/ax-profiles.md § Save Credentials for Future Use.