scaffold-marketplace

Scaffold Marketplace

Role: implementation. Lay down the marketplace catalog and the release wiring that keeps it in sync, then seed at least one plugin slot.

Constraints

1. Catalog format is fixed. .claude-plugin/marketplace.json must match the structure in docs/marketplace-builder-plugin-playbook.md §2.1 — name, owner, and a plugins[] array of git-subdir source entries.
2. At least one plugin slot. A marketplace with no plugins is not done; scaffold a first plugin entry (via --first-plugin or a placeholder slot).
3. Versioning is automated, never hand-edited. Every catalog entry's version and source.ref are owned by release-please extra-files. Do not ask the user to maintain them by hand.
4. Never overwrite an existing catalog. If .claude-plugin/marketplace.json exists, report and stop (offer /scaffold-plugin to add a plugin instead).

Step 1 — Parse

• OWNER = $0 (the marketplace name / owner handle).
• FIRST = --first-plugin value, else example-plugin (a placeholder slot the user renames).
• If .claude-plugin/marketplace.json exists → stop.

Step 2 — Write the catalog

.claude-plugin/marketplace.json:

{
  "metadata": { "description": "<one-line marketplace description>" },
  "name": "<OWNER>",
  "owner": { "name": "<OWNER full name>" },
  "plugins": [
    {
      "author": { "name": "<OWNER full name>" },
      "description": "<FIRST plugin description>",
      "homepage": "https://github.com/<org>/<repo>",
      "license": "MIT",
      "name": "<FIRST>",
      "repository": "https://github.com/<org>/<repo>",
      "source": {
        "path": "plugins/<FIRST>",
        "ref": "<FIRST>-v0.1.0",
        "source": "git-subdir",
        "url": "https://github.com/<org>/<repo>.git"
      },
      "version": "0.1.0"
    }
  ]
}

Each entry's version and source.ref stay in lock-step with the plugin's own plugin.json and its release tag — wired in Step 4, never hand-edited.