Generate plugin manifests from shared metadata source

[robinandeer]

Problem

Plugin metadata (name, version, description, keywords) is maintained separately in .cursor-plugin/plugin.json and .claude-plugin/plugin.json. They've already drifted: Cursor was at version 1.0.1 while Claude was at 1.2.0, descriptions differed, and keywords were inconsistent.

Solution

Add a single plugin-metadata.json as the source of truth and a zero-dependency build script (scripts/build-manifests.mjs) that generates both platform manifests from it. Supports --check mode for CI.

Borrowed from vercel/vercel-plugin which treats manifest files as generated build outputs rather than hand-edited copies.

How to test

1. Edit plugin-metadata.json (e.g. bump version)
2. Run node scripts/build-manifests.mjs
3. Both .cursor-plugin/plugin.json and .claude-plugin/plugin.json reflect the change
4. Run node scripts/build-manifests.mjs --check — exits 0 if manifests are up to date, exits 1 if stale

Made with Cursor