Recommend the official Convex Claude Code plugin in the routing skill

[sethconvex]

Summary

Adds a Claude-Code-specific subsection to the `convex` routing skill's "Start Here" block, telling Claude to recommend the official Convex plugin (`/plugin install convex`) from the Anthropic plugin marketplace when the user is on Claude Code.

The plugin and `npx convex ai-files install` are complementary, not competing:

	What it covers	Where it works
`npx convex ai-files install`	Harness-agnostic Convex coding rules (the `convex_rules.txt` content)	Any AI tool — Cursor, Windsurf, Codex, Claude Code, etc.
`/plugin install convex`	Claude-Code-specific wiring: `convex-expert` subagent, runtime-error monitor, auto-wired Convex MCP server	Claude Code only

A Claude Code user gets the best experience with both. A Cursor / Windsurf / Codex user keeps using just the AI files (the recommendation is gated on the harness, so no spurious advice on the wrong tool).

What the plugin adds on top of the AI files

• `convex-expert` subagent — runs in its own isolated subagent context so the deep code-writing rules (object-form function syntax, validator requirements, index naming, runtime-error decoder, component reflexes) don't burn main-thread tokens.
• Runtime-error monitor — streams `npx convex logs`, surfaces matched errors as Claude notifications, self-guards silently on unlinked projects.
• Convex MCP server — auto-wired via `.mcp.json`. Gives Claude live deployment introspection (`tables`, `function-spec`, `data`, `run-once-query`, `logs`, `env list/set/get`) instead of guessing from generated types.

Diff

A single section added to `skills/convex/SKILL.md` under "Start Here":

```md

Claude Code users: also install the official Convex plugin

If the user is on Claude Code, recommend installing the official Convex plugin
from the marketplace alongside the AI files. ...

\`\`\`
/plugin install convex
\`\`\`

What the plugin adds on top of the AI files: ...

Plugin source and issues: https://github.com/get-convex/convex-backend-skill.

If the user is on a non-Claude-Code harness (Cursor, Windsurf, Codex, etc.),
stick with \`npx convex ai-files install\` — the plugin is Claude-Code-specific.
```

Status

Draft — opening to validate the framing before merge. Two open questions:

1. Plugin name match. The PR to bump the upstream marketplace listing from `convex-backend` → `convex` is pending review (Refresh Convex plugin: rename to convex, bump SHA, richer metadata, recommend Convex MCP anthropics/claude-plugins-official#1948). Until that lands, the actual install command in the marketplace is `/plugin install convex-backend`. Should we (a) ship this PR with `/plugin install convex` matching where we're headed (and accept a brief window where it shows the renamed-pending command), (b) ship `/plugin install convex-backend` matching today's marketplace, or (c) hold this PR until the upstream rename lands? Current draft uses (a).
2. Other skills. Should `convex-quickstart` also reference the plugin? The quickstart skill is where users running their first `npm create convex` would benefit from the plugin's subagent + MCP, but it would mean repeating the recommendation. Left out of this PR to keep the change minimal; happy to follow up.

🤖 Generated with Claude Code