Feature: Repository-level plugin recommendations (like VS Code's extensions.json)

Feature Request: Repository-level Plugin Recommendations

Add support for repository-level plugin recommendations, similar to VS Code's .vscode/extensions.json workspace extension recommendations.

Use Case

When a developer clones a repository that uses specific Claude Code plugins, they should be prompted to install those plugins automatically - just like VS Code suggests workspace extensions.

Example scenario:

1. Repository uses the todo plugin for task management
2. Co-developer clones the repo and opens it in Claude Code
3. Claude Code detects .claude/recommended-plugins.json
4. Claude Code checks if todo plugin is installed
5. If not installed → Shows UI prompt: "This project recommends the 'todo' plugin. Install?"

Proposed Implementation

Configuration File: .claude/recommended-plugins.json

{
  "recommendations": [
    "todo@codemedic",
    "code-review@superpowers",
    "github-pr@core"
  ],
  "unwantedRecommendations": [
    "legacy-plugin@old-author"
  ]
}

User Experience

On repository open:

┌─────────────────────────────────────────────────────┐
│ This workspace recommends plugins                    │
│                                                      │
│ ☐ todo@codemedic                                    │
│   Markdown-based TODO management                    │
│                                                      │
│ ☐ code-review@superpowers                           │
│   Code review workflows                             │
│                                                      │
│ [Install Selected]  [Install All]  [Don't Show]    │
└─────────────────────────────────────────────────────┘

Settings:

• claude.plugins.ignoreRecommendations - Disable all workspace recommendations
• claude.plugins.showRecommendationsOnlyOnce - Don't re-prompt after dismissal

Alternative Configuration Locations

Could also support:

1. In plugin.json (for plugin authors to recommend complementary plugins)
2. In CLAUDE.md (using frontmatter or a dedicated section)
3. In .claude/config.json (workspace-level settings)

Comparison to VS Code

VS Code's .vscode/extensions.json:

{
  "recommendations": ["ms-python.python", "ms-toolsai.jupyter"],
  "unwantedRecommendations": ["ms-vscode.csharp"]
}

Claude Code should have equivalent functionality for the plugin ecosystem.

Benefits

1. Onboarding - New team members automatically get the right plugins
2. Consistency - Entire team uses the same tooling
3. Discovery - Developers learn about useful plugins for specific workflows
4. Documentation - The recommended plugins list serves as implicit documentation of project tooling

Related Features

This could be extended to:

• Plugin version constraints ("todo@codemedic": ">=1.0.0")
• Required vs optional recommendations (warning vs info)
• Auto-install mode for CI/CD environments
• Organization-level plugin policies

Why This Matters

Many projects have specific workflows that depend on Claude Code plugins (task management, code review, deployment). Without repository-level recommendations, every developer must:

1. Discover which plugins the team uses
2. Manually search the marketplace
3. Remember to install them

This creates friction and inconsistency across teams.

---

Related to: #25150 (plugin namespace display issue)