Guide

Linear plugin labels

PRC Engineering uses a Plugin label group with one child label per top-level prc-* npm workspace in package.json (plugins/prc-<slug>/).

Using labels

  • Tag issues with the plugin slug label (e.g. prc-block-library) when work is scoped to that plugin.
  • Filter issues with label:prc-chart-builder or pick from the Plugin group in the label picker.

After adding or renaming top-level plugins/prc-* workspaces in package.json, run the Cursor command:

/sync-linear-plugin-labels

Preview changes without writing to Linear:

/sync-linear-plugin-labels --dry-run

The command reads workspaces from package.json, compares them to PRC Engineering labels via the Linear MCP plugin, creates missing Plugin children, and reports any flat prc-* labels that need manual reparenting in Linear.

Command source: .cursor/commands/sync-linear-plugin-labels.md.

Adding a single label manually

For one-off creates without the command, use Linear MCP create_issue_label with name prc-<slug>, parent Plugin, teamId for PRC Engineering, and description PRC Platform plugin: plugins/prc-<slug>/.

Manual cleanup

If a plugin label existed before the group was created (e.g. prc-newsletter-builder), move it under Plugin in Linear: Settings → Teams → PRC Engineering → Issue labels.

Canonical plugin list

Top-level workspaces only (not nested packages):

node -e "const p=require('./package.json'); console.log(p.workspaces.filter(w=>/^plugins\\/prc-[^/]+$/.test(w)).map(w=>w.replace('plugins/','')).sort().join('\n'))"

Was this helpful?