Introducing a new way to review your PRs.

Read the announcement

cathrynlavery / diagram-design

Editorial diagram design for Claude Code, Codex, GitHub Copilot, Cursor, Factory Droid, Qoder, and Pi. 45 diagram types. Self-contained HTML + SVG. No shadows. No Mermaid slop.

View on GitHub

23 documents · Updated Nov 20, 2026

docs / plugin-distribution

Plugin distribution and host integration

The diagram-design capability is one package with native entry points for Claude, Codex, Factory, and Qoder. Each host uses its own plugin root and manifest shape, while the shared package identity is intended to keep the diagram capability and release version aligned across hosts.

Package boundary

Shared plugin identity

The shared plugin identity tells each host that it is installing the same diagram-design product. The Claude manifest now carries version 2.6.168, while the Factory and Qoder manifests carry 2.6.148 and the Codex manifest described by the prior aligned release carries 2.6.136; this version split means the package identity is not currently aligned across hosts.

References: .claude-plugin/plugin.json• L1-27 .codex-plugin/plugin.json• L1-24 .factory-plugin/plugin.json• L1-25 .qoder-plugin/plugin.json• L1-27

Host entry points

Each host has a native entry point in its own plugin root. The roots keep host discovery separate while the manifests connect each host to the same package identity. Claude and Factory use a compact identity manifest. Codex adds skill and interface metadata, while Qoder adds the command and skill roots used by its host.

HostNative entry pointHost-specific purpose
Claude.claude-plugin/plugin.jsonNames the package for Claude installation
Codex.codex-plugin/plugin.jsonAdds the skill path and user-facing interface
Factory.factory-plugin/plugin.jsonNames the package for Factory installation
Qoder.qoder-plugin/plugin.jsonAdds the command and skill paths for Qoder

References: .claude-plugin/plugin.json• L1-27 .codex-plugin/plugin.json• L1-47 .factory-plugin/plugin.json• L1-25 .qoder-plugin/plugin.json• L1-27

Host integration

Claude integration

Claude uses its native plugin manifest to identify the package and its broad diagram scope. The manifest presents editorial diagrams in HTML and SVG, supports many diagram types, redraws common diagram sources, and exports SVG and PNG without defining a separate diagram implementation.

References: .claude-plugin/plugin.json• L1-27

Codex integration

Codex uses its manifest to connect the package to the shared skills directory and to present a diagram-focused interface. Its interface describes the product as a tool that creates editorial diagrams from system, process, or data descriptions and can redraw common diagram sources.

The interface also declares read and write capabilities. Default prompts guide common entry points such as architecture diagrams, decision flowcharts, and Mermaid redraws.

References: .codex-plugin/plugin.json• L25-46

Factory integration

Factory uses its native plugin manifest to identify the same diagram-design package. It shares the product identity and release metadata with the other host manifests, which is intended to keep host listings aligned.

References: .factory-plugin/plugin.json• L1-25

Qoder integration

Qoder uses its native plugin manifest to identify the same diagram-design package and locate its commands and skills. Its extra root metadata connects Qoder discovery to the shared package content without creating a separate product identity.

References: .qoder-plugin/plugin.json• L1-27

Marketplace metadata

Marketplace metadata connects a host listing to the package identity. The Claude marketplace file names the marketplace, describes the diagram capability, identifies its owner, and points the listing to the package root. The host manifests provide the common product contract, while host-specific fields provide the install and presentation information for that host.

The shared contract includes:

  • Package name and diagram capability description
  • Release version
  • Author, home page, repository, and license
  • Search keywords for diagram work

Codex adds interface metadata because it presents the package as a richer user-facing capability. That metadata includes its display name, category, supported actions, prompts, brand assets, and privacy link. Qoder instead adds content-root metadata so its host can find commands and skills.

References: .claude-plugin/marketplace.json• L1-14 .claude-plugin/plugin.json• L1-27 .codex-plugin/plugin.json• L1-47 .factory-plugin/plugin.json• L1-25 .qoder-plugin/plugin.json• L25-27

Package flow

Host discovery

Host discovery starts with a native manifest and uses the host marketplace rules to make the diagram-design package available. The result is one product identity presented through four host-specific entry points.

This diagram shows how native host metadata leads to one shared diagram capability.

flowchart LR
    A[Claude entry point] --> D[Diagram-design package]
    B[Codex entry point] --> D
    C[Factory entry point] --> D
    F[Qoder entry point] --> D
    D --> E[Shared diagram capability]

References: .claude-plugin/plugin.json• L1-27 .codex-plugin/plugin.json• L1-47 .factory-plugin/plugin.json• L1-25 .qoder-plugin/plugin.json• L1-27

Release alignment

The four manifests must move as one release set. The changed Claude manifest now reports 2.6.168, while the Factory and Qoder manifests report 2.6.148 and the Codex manifest described by the prior release alignment reports 2.6.136; until those values move together, hosts can describe different package releases.

See Plugin release automation for the release process and Plugin manifest validation for the checks that protect host metadata contracts.

References: .claude-plugin/plugin.json• L4 .codex-plugin/plugin.json• L4 .factory-plugin/plugin.json• L4 .qoder-plugin/plugin.json• L4

Change checklist

When these files or sections are changed, remember to consider these:

  • Keep the shared identity fields and version equal across all four native manifests.
  • Keep the Claude marketplace name, description, owner, and package source aligned with the Claude plugin identity.
  • Keep Codex interface data aligned with the diagram capability and its supported actions.
  • Keep Qoder command and skill roots aligned with the package content.
  • Update host marketplace metadata when a host entry point or install contract changes.
  • Check the release and validation pages when a manifest field changes.

Important failure modes

TriggerConsequenceGuard
One host manifest keeps an older or newer versionHosts can report different releases for the same packageSynchronized manifest version checks
Shared identity metadata divergesMarketplace listings can describe different productsCross-host identity validation
Claude marketplace metadata points to the wrong package rootClaude discovery can install or expose the wrong packageMarketplace source and manifest checks
Codex interface data no longer matches the capabilityCodex users receive incorrect prompts or permission informationCodex manifest validation
Qoder points to a missing command or skill rootQoder can install the package but fail to expose its capabilitiesQoder root-path validation
A host marketplace entry does not resolve to the packageInstallation or discovery can fail for that hostMarketplace source and manifest checks

Key files

FileWhy to read it
.claude-plugin/plugin.jsonShows the shared package identity and Claude release version
.claude-plugin/marketplace.jsonShows the Claude marketplace listing and package source
.codex-plugin/plugin.jsonShows the shared identity plus Codex interface metadata
.factory-plugin/plugin.jsonShows the shared package identity for Factory
.qoder-plugin/plugin.jsonShows the shared identity plus Qoder command and skill roots
docs/plugin-release-automation.mdExplains how host package versions move together
docs/plugin-manifest-validation.mdExplains the checks for manifest and marketplace contracts