@adia-ai/adia-plugins

This package is a Claude Code plugin-marketplace manifest — not a plugin itself. It exists so anyone, with no access to Adia's private source repo, can discover and install the two adia-ui Claude Code plugins:

• adia-ui-kit-forge — maintain the adia-ui (@adia-ai) framework itself: author primitives and shells, run the A2UI generation pipeline, review gen-UI quality, sweep QA, cut releases, deploy.
• adia-ui-kit-factory — author and verify apps built ON adia-ui: orient, scaffold, compose, wire, verify, migrate, across SPA/SSR/hybrid hosts.

Realizes ADR-0045 — npm is the sole distribution channel for this manifest; there is deliberately no public git repo. The manifest itself, marketplace.json, ships at this package's root.

Install

Requires Node + npm (npm-sourced plugin entries install via npm install):

node --version && npm --version

claude
/plugin marketplace add https://unpkg.com/@adia-ai/adia-plugins/marketplace.json
/plugin install adia-ui-kit-factory@adia-plugins
/plugin install adia-ui-kit-forge@adia-plugins

No gh auth, no .npmrc token, no adiahealth org membership required — the manifest and both plugins resolve entirely off the public npm registry.

Both plugin entries are unpinned ({"source": "npm", "package": "@adia-ai/adia-ui-forge"}, no version), so an install always tracks each plugin's currently-published latest; a routine plugin cut needs no manifest republish here. Version authority stays each plugin's own package.json / .claude-plugin/plugin.json.

Install (OpenAI Codex)

Codex plugins ship a different manifest shape than Claude Code (.codex-plugin/plugin.json + agents/openai.yaml, verified 2026-08-23 against the bundled plugins under ~/.codex/.tmp/bundled-marketplaces/ and ~/.cache/codex-runtimes/) — both adia-ui-kit-forge and adia-ui-kit-factory ship one alongside their existing Claude manifest, additively (AGENTS.md's "Non-Claude harnesses" note).

🟡 Every Codex marketplace entry observed so far — bundled and runtime-cached — uses "source": "local"; none uses an "npm" source. Rather than guess at an unverified npm source type, this package's Codex marketplace (.agents/plugins/marketplace.json) sources both plugins local, at the npm-installed layout — same npm distribution channel as the Claude marketplace above, honest about the one extra step Codex needs:

mkdir adia-codex-plugins && cd adia-codex-plugins
npm install @adia-ai/adia-plugins @adia-ai/adia-ui-forge @adia-ai/adia-ui-factory

Then point Codex at the installed marketplace manifest:

# ~/.codex/config.toml
[marketplaces.adia-local]
path = "/absolute/path/to/adia-codex-plugins/node_modules/@adia-ai/adia-plugins/.agents/plugins/marketplace.json"

[plugins."adia-ui-kit-forge@adia-local"]
enabled = true

[plugins."adia-ui-kit-factory@adia-local"]
enabled = true

The manifest's local paths (./node_modules/@adia-ai/adia-ui-forge, ./node_modules/@adia-ai/adia-ui-factory) resolve relative to the adia-codex-plugins install root, which is why both plugins must sit in that same npm install alongside @adia-ai/adia-plugins — a routine cut still needs no manifest republish here (both plugins ride their own .codex-plugin/plugin.json version, same unpinned-latest discipline as the Claude marketplace).

Install (Hermes / Pi)

Neither harness uses a marketplace-manifest shape — each plugin ships its Hermes and Pi manifests directly inside its own npm package (gh#1954), so this package's marketplace.json doesn't apply to either path:

npm install @adia-ai/adia-ui-forge @adia-ai/adia-ui-factory

• Hermes — point plugin loading at the installed node_modules/@adia-ai/adia-ui-forge (or -factory) directory; each ships plugin.yaml + __init__.py at its package root. 🟡 MCP is user-level config in Hermes, not a plugin field — merge the generated hermes-mcp.yaml into your own ~/.hermes/config.yaml by hand; there is no automatic wiring.
• Pi — discovered via the pi-package keyword and the "pi" field in each plugin's package.json; prompts/*.md gives every /command a genuine Pi prompt template. 🟡 Pi core has no native MCP support at all — the adia-gen-ui / adia-factory MCP servers only reach Pi through the third-party pi-mcp-adapter package, which reads each plugin's .mcp.json unmodified. Without that adapter, the MCP-backed tools silently do nothing on a stock Pi install.

Neither harness has a hooks/agents surface — see each plugin's own README ("Non-Claude harnesses" section) for the full per-harness degradation table.

Editors — Zed, Cursor, VS Code

Two paths, same underlying MCP story as Hermes/Pi above: wire the @adia-ai/mcp servers into the editor's own MCP config (Cursor: .cursor/mcp.json, or global MCP settings; VS Code: .vscode/mcp.json, Copilot agent mode; Zed: settings.json's context-server section) for the tool surface with no Claude-shaped skills/commands — or run Claude Code inside the editor (Cursor/VS Code via the Claude Code extension or an integrated terminal; Zed's agent panel connects Claude Code as an external agent) for the full plugin, installed via the marketplace flow above. Full platform matrix and walkthrough: Factory Plugin — Zed, Cursor, and VS Code.

Feedback / bugs

This package carries no source code — file a report against whichever plugin you're actually using:

npm view @adia-ai/adia-ui-factory bugs
npm view @adia-ai/adia-ui-forge bugs

Both resolve to { email: "[email protected]" } — triage owner: kimba. If you hit this from inside a Claude Code session, the factory plugin's report_issue MCP tool writes a local ticket (qa/findings/issues/<id>.md + .json); attach the generated markdown to that address — it does not transmit anywhere on its own.

What this is not

• Not a Claude Code plugin — no .claude-plugin/plugin.json, no skills//agents/commands/. npm install gets you marketplace.json and this README; nothing loads into a Claude Code session from this package directly.
• Not a public git surface. This package, and both plugins it sources, are distributed only through the npm registry — there is no adiahealth/adia-plugins-style repo to clone, star, or file issues against, and none is planned (ADR-0045 Decision 3).