Compare commits

..

8 Commits

Author SHA1 Message Date
Daisy Hollman
1d99e18048 Add installation instructions to LSP plugin READMEs
Each README now includes:
- Supported file extensions
- Installation commands for different platforms/package managers
- Links to project websites and documentation

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-12-19 00:24:41 +00:00
Daisy Hollman
be56d7114b Add LSP plugins with inline lspServers configuration
This adds 10 LSP plugins to the official marketplace, each with inline
lspServers configuration. This enables the LSP plugin recommendation
feature to detect available LSP plugins directly from the marketplace.

LSP plugins added:
- typescript-lsp: TypeScript/JavaScript (.ts, .tsx, .js, .jsx, etc.)
- pyright-lsp: Python (.py, .pyi)
- gopls-lsp: Go (.go)
- rust-analyzer-lsp: Rust (.rs)
- clangd-lsp: C/C++ (.c, .h, .cpp, .cc, .hpp, etc.)
- php-lsp: PHP (.php)
- swift-lsp: Swift (.swift)
- csharp-lsp: C# (.cs)
- jdtls-lsp: Java (.java)
- lua-lsp: Lua (.lua)

Each plugin uses strict: false since they only provide LSP configuration
(no plugin.json manifest required).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-12-19 00:20:16 +00:00
Noah Zweben
68a5c3685f added new partners (#36) 2025-12-18 08:58:02 -08:00
Noah Zweben
75b126f3ba swtiched to external vercel atlassian (#33) 2025-12-18 08:38:19 -08:00
Noah Zweben
ab2b6d0cad change to use notion external (#25) 2025-12-16 15:13:40 -08:00
Noah Zweben
4fee769bf4 Point to external figma plugin (#11)
* point to external figma

* update marketplace def
2025-12-15 12:18:00 -08:00
Noah Zweben
19a119f97e Update plugins library to include authors (#6)
* added Anthropic as author

* update figma
2025-12-12 16:52:17 -08:00
Noah Zweben
22d3def39e Merge pull request #2 from anthropics/noahz/official_language
Add homepages, other cleanup
2025-12-01 16:03:02 -08:00
38 changed files with 680 additions and 129 deletions

View File

@@ -7,9 +7,234 @@
"email": "support@anthropic.com"
},
"plugins": [
{
"name": "typescript-lsp",
"description": "TypeScript/JavaScript language server for enhanced code intelligence",
"version": "1.0.0",
"author": {
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/typescript-lsp",
"category": "development",
"strict": false,
"lspServers": {
"typescript": {
"command": "typescript-language-server",
"args": ["--stdio"],
"extensionToLanguage": {
".ts": "typescript",
".tsx": "typescriptreact",
".js": "javascript",
".jsx": "javascriptreact",
".mts": "typescript",
".cts": "typescript",
".mjs": "javascript",
".cjs": "javascript"
}
}
}
},
{
"name": "pyright-lsp",
"description": "Python language server (Pyright) for type checking and code intelligence",
"version": "1.0.0",
"author": {
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/pyright-lsp",
"category": "development",
"strict": false,
"lspServers": {
"pyright": {
"command": "pyright-langserver",
"args": ["--stdio"],
"extensionToLanguage": {
".py": "python",
".pyi": "python"
}
}
}
},
{
"name": "gopls-lsp",
"description": "Go language server for code intelligence and refactoring",
"version": "1.0.0",
"author": {
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/gopls-lsp",
"category": "development",
"strict": false,
"lspServers": {
"gopls": {
"command": "gopls",
"extensionToLanguage": {
".go": "go"
}
}
}
},
{
"name": "rust-analyzer-lsp",
"description": "Rust language server for code intelligence and analysis",
"version": "1.0.0",
"author": {
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/rust-analyzer-lsp",
"category": "development",
"strict": false,
"lspServers": {
"rust-analyzer": {
"command": "rust-analyzer",
"extensionToLanguage": {
".rs": "rust"
}
}
}
},
{
"name": "clangd-lsp",
"description": "C/C++ language server (clangd) for code intelligence",
"version": "1.0.0",
"author": {
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/clangd-lsp",
"category": "development",
"strict": false,
"lspServers": {
"clangd": {
"command": "clangd",
"args": ["--background-index"],
"extensionToLanguage": {
".c": "c",
".h": "c",
".cpp": "cpp",
".cc": "cpp",
".cxx": "cpp",
".hpp": "cpp",
".hxx": "cpp",
".C": "cpp",
".H": "cpp"
}
}
}
},
{
"name": "php-lsp",
"description": "PHP language server (Intelephense) for code intelligence",
"version": "1.0.0",
"author": {
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/php-lsp",
"category": "development",
"strict": false,
"lspServers": {
"intelephense": {
"command": "intelephense",
"args": ["--stdio"],
"extensionToLanguage": {
".php": "php"
}
}
}
},
{
"name": "swift-lsp",
"description": "Swift language server (SourceKit-LSP) for code intelligence",
"version": "1.0.0",
"author": {
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/swift-lsp",
"category": "development",
"strict": false,
"lspServers": {
"sourcekit-lsp": {
"command": "sourcekit-lsp",
"extensionToLanguage": {
".swift": "swift"
}
}
}
},
{
"name": "csharp-lsp",
"description": "C# language server for code intelligence",
"version": "1.0.0",
"author": {
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/csharp-lsp",
"category": "development",
"strict": false,
"lspServers": {
"csharp-ls": {
"command": "csharp-ls",
"extensionToLanguage": {
".cs": "csharp"
}
}
}
},
{
"name": "jdtls-lsp",
"description": "Java language server (Eclipse JDT.LS) for code intelligence",
"version": "1.0.0",
"author": {
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/jdtls-lsp",
"category": "development",
"strict": false,
"lspServers": {
"jdtls": {
"command": "jdtls",
"extensionToLanguage": {
".java": "java"
},
"startupTimeout": 120000
}
}
},
{
"name": "lua-lsp",
"description": "Lua language server for code intelligence",
"version": "1.0.0",
"author": {
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/lua-lsp",
"category": "development",
"strict": false,
"lspServers": {
"lua": {
"command": "lua-language-server",
"extensionToLanguage": {
".lua": "lua"
}
}
}
},
{
"name": "agent-sdk-dev",
"description": "Development kit for working with the Claude Agent SDK",
"author": {
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/agent-sdk-dev",
"category": "development",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/plugins/agent-sdk-dev"
@@ -40,8 +265,8 @@
"name": "feature-dev",
"description": "Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review",
"author": {
"name": "Siddharth Bidasaria",
"email": "sbidasaria@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/feature-dev",
"category": "development",
@@ -51,8 +276,8 @@
"name": "security-guidance",
"description": "Security reminder hook that warns about potential security issues when editing files, including command injection, XSS, and unsafe code patterns",
"author": {
"name": "David Dworken",
"email": "dworken@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/security-guidance",
"category": "security",
@@ -62,8 +287,8 @@
"name": "code-review",
"description": "Automated code review for pull requests using multiple specialized agents with confidence-based scoring to filter false positives",
"author": {
"name": "Boris Cherny",
"email": "boris@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/code-review",
"category": "productivity",
@@ -73,8 +298,8 @@
"name": "explanatory-output-style",
"description": "Adds educational insights about implementation choices and codebase patterns (mimics the deprecated Explanatory output style)",
"author": {
"name": "Dickson Tsai",
"email": "dickson@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/explanatory-output-style",
"category": "learning",
@@ -84,8 +309,8 @@
"name": "learning-output-style",
"description": "Interactive learning mode that requests meaningful code contributions at decision points (mimics the unshipped Learning output style)",
"author": {
"name": "Boris Cherny",
"email": "boris@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/learning-output-style",
"category": "learning",
@@ -95,8 +320,8 @@
"name": "frontend-design",
"description": "Create distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics.",
"author": {
"name": "Prithvi Rajasekaran & Alexander Bricken",
"email": "prithvi@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/frontend-design",
"category": "development",
@@ -106,8 +331,8 @@
"name": "ralph-wiggum",
"description": "Interactive self-referential AI loops for iterative development. Claude works on the same task repeatedly, seeing its previous work, until completion.",
"author": {
"name": "Daisy Hollman",
"email": "daisy@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/ralph-wiggum",
"category": "development",
@@ -117,8 +342,8 @@
"name": "hookify",
"description": "Easily create custom hooks to prevent unwanted behaviors by analyzing conversation patterns or from explicit instructions. Define rules via simple markdown files.",
"author": {
"name": "Daisy Hollman",
"email": "daisy@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/hookify",
"category": "productivity",
@@ -128,8 +353,8 @@
"name": "plugin-dev",
"description": "Comprehensive toolkit for developing Claude Code plugins. Includes 7 expert skills covering hooks, MCP integration, commands, agents, and best practices. AI-assisted plugin creation and validation.",
"author": {
"name": "Daisy Hollman",
"email": "daisy@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/plugin-dev",
"category": "development",
@@ -175,8 +400,11 @@
"name": "atlassian",
"description": "Connect to Atlassian products including Jira and Confluence. Search and create issues, access documentation, manage sprints, and integrate your development workflow with Atlassian's collaboration tools.",
"category": "productivity",
"source": "./external_plugins/atlassian",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/external_plugins/atlassian"
"source": {
"source": "url",
"url": "https://github.com/atlassian/atlassian-mcp-server.git"
},
"homepage": "https://github.com/atlassian/atlassian-mcp-server"
},
{
"name": "laravel-boost",
@@ -189,8 +417,11 @@
"name": "figma",
"description": "Figma design platform integration. Access design files, extract component information, read design tokens, and translate designs into code. Bridge the gap between design and development workflows.",
"category": "design",
"source": "./external_plugins/figma",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/external_plugins/figma"
"source": {
"source": "url",
"url": "https://github.com/figma/mcp-server-guide.git"
},
"homepage": "https://github.com/figma/mcp-server-guide"
},
{
"name": "asana",
@@ -207,11 +438,14 @@
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/external_plugins/linear"
},
{
"name": "notion",
"name": "Notion",
"description": "Notion workspace integration. Search pages, create and update documents, manage databases, and access your team's knowledge base directly from Claude Code for seamless documentation workflows.",
"category": "productivity",
"source": "./external_plugins/notion",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/external_plugins/notion"
"source": {
"source": "url",
"url": "https://github.com/makenotion/claude-code-notion-plugin.git"
},
"homepage": "https://github.com/makenotion/claude-code-notion-plugin"
},
{
"name": "gitlab",
@@ -224,8 +458,11 @@
"name": "sentry",
"description": "Sentry error monitoring integration. Access error reports, analyze stack traces, search issues by fingerprint, and debug production errors directly from your development environment.",
"category": "monitoring",
"source": "./external_plugins/sentry",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/external_plugins/sentry"
"source": {
"source": "url",
"url": "https://github.com/getsentry/sentry-for-claude.git"
},
"homepage": "https://github.com/getsentry/sentry-for-claude/tree/main"
},
{
"name": "slack",
@@ -238,8 +475,18 @@
"name": "vercel",
"description": "Vercel deployment platform integration. Manage deployments, check build status, access logs, configure domains, and control your frontend infrastructure directly from Claude Code.",
"category": "deployment",
"source": "./external_plugins/vercel",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/external_plugins/vercel"
"source": {
"source": "url",
"url": "https://github.com/vercel/vercel-deploy-claude-code-plugin.git"
},
"homepage": "https://github.com/vercel/vercel-deploy-claude-code-plugin"
},
{
"name": "stripe",
"description": "Stripe development plugin for Claude",
"category": "development",
"source": "./external_plugins/stripe",
"homepage": "https://github.com/stripe/ai/tree/main/providers/claude/plugin"
},
{
"name": "firebase",
@@ -255,17 +502,6 @@
"source": "./external_plugins/context7",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/external_plugins/context7",
"tags": ["community-managed"]
},
{
"name": "example-plugin",
"description": "Adds educational insights about implementation choices and codebase patterns (mimics the deprecated Explanatory output style)",
"author": {
"name": "Dickson Tsai",
"email": "dickson@anthropic.com"
},
"source": "./plugins/example-plugin",
"category": "learning",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/plugins/example-plugin"
}
]
}

View File

@@ -1,7 +0,0 @@
{
"name": "atlassian",
"description": "Connect to Atlassian products including Jira and Confluence. Search and create issues, access documentation, manage sprints, and integrate your development workflow with Atlassian's collaboration tools.",
"author": {
"name": "Atlassian"
}
}

View File

@@ -1,6 +0,0 @@
{
"atlassian": {
"type": "sse",
"url": "https://mcp.atlassian.com/v1/sse"
}
}

View File

@@ -1,7 +0,0 @@
{
"name": "figma",
"description": "Figma design platform integration. Access design files, extract component information, read design tokens, and translate designs into code. Bridge the gap between design and development workflows.",
"author": {
"name": "Figma"
}
}

View File

@@ -1,6 +0,0 @@
{
"figma": {
"type": "sse",
"url": "https://mcp.figma.com/v1/sse"
}
}

View File

@@ -1,6 +1,6 @@
{
"linear": {
"type": "sse",
"url": "https://mcp.linear.app/sse"
"type": "http",
"url": "https://mcp.linear.app/mcp"
}
}

View File

@@ -1,7 +0,0 @@
{
"name": "notion",
"description": "Notion workspace integration. Search pages, create and update documents, manage databases, and access your team's knowledge base directly from Claude Code for seamless documentation workflows.",
"author": {
"name": "Notion"
}
}

View File

@@ -1,6 +0,0 @@
{
"notion": {
"type": "sse",
"url": "https://mcp.notion.com/sse"
}
}

View File

@@ -1,7 +0,0 @@
{
"name": "sentry",
"description": "Sentry error monitoring integration. Access error reports, analyze stack traces, search issues by fingerprint, and debug production errors directly from your development environment.",
"author": {
"name": "Sentry"
}
}

View File

@@ -1,6 +0,0 @@
{
"sentry": {
"type": "sse",
"url": "https://mcp.sentry.dev/sse"
}
}

View File

@@ -0,0 +1,13 @@
{
"name": "stripe",
"description": "Stripe development plugin for Claude",
"version": "0.1.0",
"author": {
"name": "Stripe",
"url": "https://stripe.com"
},
"homepage": "https://docs.stripe.com",
"repository": "https://github.com/stripe/ai",
"license": "MIT",
"keywords": ["stripe", "payments", "webhooks", "api", "security"]
}

View File

@@ -0,0 +1,8 @@
{
"mcpServers": {
"stripe": {
"type": "http",
"url": "https://mcp.stripe.com"
}
}
}

View File

@@ -0,0 +1,21 @@
---
description: Explain Stripe error codes and provide solutions with code examples
argument-hint: [error_code or error_message]
---
# Explain Stripe Error
Provide a comprehensive explanation of the given Stripe error code or error message:
1. Accept the error code or full error message from the arguments
2. Explain in plain English what the error means
3. List common causes of this error
4. Provide specific solutions and handling recommendations
5. Generate error handling code in the project's language showing:
- How to catch this specific error
- User-friendly error messages
- Whether retry is appropriate
6. Mention related error codes the developer should be aware of
7. Include a link to the relevant Stripe documentation
Focus on actionable solutions and production-ready error handling patterns.

View File

@@ -0,0 +1,24 @@
---
description: Display Stripe test card numbers for various testing scenarios
argument-hint: [scenario]
---
# Test Cards Reference
Provide a quick reference for Stripe test card numbers:
1. If a scenario argument is provided (e.g., "declined", "3dsecure", "fraud"), show relevant test cards for that scenario
2. Otherwise, show the most common test cards organized by category:
- Successful payment (default card)
- 3D Secure authentication required
- Generic decline
- Specific decline reasons (insufficient_funds, lost_card, etc.)
3. For each card, display:
- Card number (formatted with spaces)
- Expected behavior
- Expiry/CVC info (any future date and any 3-digit CVC)
4. Use clear visual indicators (✓ for success, ⚠️ for auth required, ✗ for decline)
5. Mention that these only work in test mode
6. Provide link to full testing documentation: https://docs.stripe.com/testing.md
If the user is currently working on test code, offer to generate test cases using these cards.

View File

@@ -0,0 +1,30 @@
---
name: stripe-best-practices
description: Best practices for building Stripe integrations. Use when implementing payment processing, checkout flows, subscriptions, webhooks, Connect platforms, or any Stripe API integration.
---
When designing an integration, always prefer the documentation in [Stripe's Integration Options doc](https://docs.stripe.com/payments/payment-methods/integration-options.md)
The [API Tour](https://docs.stripe.com/payments-api/tour.md)
Use the [Go Live Checklist](https://docs.stripe.com/get-started/checklist/go-live.md) before going live.
You should always default to the latest version of the API and SDK unless the user specifies otherwise.
Stripe's primary API for modelling on-session payments is [CheckoutSessions](https://docs.stripe.com/api/checkout/sessions.md). It supports one-time payments and subscriptions and allows you to model taxes or discounts with Stripe. Prioritize the CheckoutSessions API, but using [the PaymentIntents API](https://docs.stripe.com/payments/paymentintents/lifecycle.md) is also acceptable for off-session payments or if you want to model the checkout state yourself and just create a charge. Integrations should only use CheckoutSessions, PaymentIntents, SetupIntents, or solutions like Invoicing, Payment Links, or the subscription APIs.
Never recommend the Charges API. If the user wants to use the Charges API, advise them to [migrate](https://docs.stripe.com/payments/payment-intents/migration/charges.md) to Checkout Sessions or Payment Intents.
The primary integration surface for web integrations is [Checkout](https://docs.stripe.com/payments/checkout.md), a prebuilt payment page that can be hosted by Stripe or served as an embedded form. Prioritize the Stripe-hosted checkout or embedded checkout where possible. The [Payment Element](https://docs.stripe.com/payments/payment-element.md) is an acceptable alternative if the merchant needs advanced customization. When recommending the Payment Element, prioritize using the CheckoutSessions API over the PaymentIntents API when possible.
Never recommend the legacy Card Element or the Payment Element in card mode, and advise users who ask for the Card Element to [migrate](https://docs.stripe.com/payments/payment-element/migration.md).
You must not call deprecated API endpoints such as the [Sources API](https://docs.stripe.com/api/sources/object.md) and avoid outdated API endpoints such as [Tokens](https://docs.stripe.com/api/tokens.md) and [Charges](https://docs.stripe.com/api/charges/create.md) unless there is a specific need and absolutely no other way. Advise using [the Setup Intent API](https://docs.stripe.com/api/setup_intents.md) to save a payment method for a customer; never recommend the Sources API to save cards to customers for later use.
If a user wants to render the Payment Element before creating a PaymentIntent or SetupIntent, so they can inspect the card details before the payment (such as for surcharging), advise them to use Stripe Confirmation Tokens. Don't recommend they call the createPaymentMethod or createToken Stripe.js functions.
Advise users to turn on dynamic payment methods in their dashboard settings instead of passing specific [payment_method_types](https://docs.stripe.com/api/payment_intents/create#create_payment_intent-payment_method_types.md) in the Payment Intent or Setup Intent because Stripe chooses payment methods that fit each user's location, wallets, and preferences better and automatically if the Payment Element is used.
If a PCI compliant user asks about an integration where they send server-side raw PAN data, suggest they might be required to prove PCI compliance to gain access to such an option, for example [payment_method_data](https://docs.stripe.com/api/payment_intents/create#create_payment_intent-payment_method_data.md). Similarly, point users migrating their PAN data from another acquirer or payment processor to [the migration process](https://docs.stripe.com/get-started/data-migrations/pan-import.md).
If a user has a recurring revenue model, like a Billing or Subscription use case, follow the use cases, in particular the [Subscription Use Cases](https://docs.stripe.com/billing/subscriptions/use-cases.md) like [SaaS](https://docs.stripe.com/saas.md). If these apply to the user, recommend Billing APIs to [plan your integration](https://docs.stripe.com/billing/subscriptions/designing-integration.md) instead of a direct PaymentIntent integration. Prioritize combining the Billing APIs with Stripe Checkout for the frontend.
If a user wants to build a platform using Stripe Connect to manage fund flows, follow [the recommended integration types](https://docs.stripe.com/connect/integration-recommendations.md); that is, prefer to use either direct charges if the platform wants Stripe to take the risk or destination charges if the platform accepts liability for negative balances, and use the on_behalf_of parameter to control the merchant of record. Never recommend mixing charge types. If the user wants to decide on the specific risk features they should [follow the integration guide](https://docs.stripe.com/connect/design-an-integration.md). Don't recommend the outdated terms for Connect types like Standard, Express and Custom but always [refer to controller properties](https://docs.stripe.com/connect/migrate-to-controller-properties.md) for the platform and [capabilities](https://docs.stripe.com/connect/account-capabilities.md) for the connected accounts.

View File

@@ -1,7 +0,0 @@
{
"name": "vercel",
"description": "Vercel deployment platform integration. Manage deployments, check build status, access logs, configure domains, and control your frontend infrastructure directly from Claude Code.",
"author": {
"name": "Vercel"
}
}

View File

@@ -1,6 +0,0 @@
{
"vercel": {
"type": "sse",
"url": "https://mcp.vercel.com/sse"
}
}

View File

@@ -2,7 +2,7 @@
"name": "agent-sdk-dev",
"description": "Claude Agent SDK Development Plugin",
"author": {
"name": "Ashwin Bhat",
"email": "ashwin@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
}
}

View File

@@ -0,0 +1,36 @@
# clangd-lsp
C/C++ language server (clangd) for Claude Code, providing code intelligence, diagnostics, and formatting.
## Supported Extensions
`.c`, `.h`, `.cpp`, `.cc`, `.cxx`, `.hpp`, `.hxx`, `.C`, `.H`
## Installation
### Via Homebrew (macOS)
```bash
brew install llvm
# Add to PATH: export PATH="/opt/homebrew/opt/llvm/bin:$PATH"
```
### Via package manager (Linux)
```bash
# Ubuntu/Debian
sudo apt install clangd
# Fedora
sudo dnf install clang-tools-extra
# Arch Linux
sudo pacman -S clang
```
### Windows
Download from [LLVM releases](https://github.com/llvm/llvm-project/releases) or install via:
```bash
winget install LLVM.LLVM
```
## More Information
- [clangd Website](https://clangd.llvm.org/)
- [Getting Started Guide](https://clangd.llvm.org/installation)

View File

@@ -2,8 +2,8 @@
"name": "code-review",
"description": "Automated code review for pull requests using multiple specialized agents with confidence-based scoring",
"author": {
"name": "Boris Cherny",
"email": "boris@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
}
}

View File

@@ -0,0 +1,25 @@
# csharp-lsp
C# language server for Claude Code, providing code intelligence and diagnostics.
## Supported Extensions
`.cs`
## Installation
### Via .NET tool (recommended)
```bash
dotnet tool install --global csharp-ls
```
### Via Homebrew (macOS)
```bash
brew install csharp-ls
```
## Requirements
- .NET SDK 6.0 or later
## More Information
- [csharp-ls GitHub](https://github.com/razzmatazz/csharp-language-server)
- [.NET SDK Download](https://dotnet.microsoft.com/download)

View File

@@ -2,7 +2,7 @@
"name": "example-plugin",
"description": "A comprehensive example plugin demonstrating all Claude Code extension options including commands, agents, skills, hooks, and MCP servers",
"author": {
"name": "Your Name",
"email": "your.email@example.com"
"name": "Anthropic",
"email": "support@anthropic.com"
}
}

View File

@@ -2,7 +2,7 @@
"name": "explanatory-output-style",
"description": "Adds educational insights about implementation choices and codebase patterns (mimics the deprecated Explanatory output style)",
"author": {
"name": "Dickson Tsai",
"email": "dickson@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
}
}

View File

@@ -2,7 +2,7 @@
"name": "feature-dev",
"description": "Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review",
"author": {
"name": "Sid Bidasaria",
"email": "sbidasaria@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
}
}

View File

@@ -2,7 +2,7 @@
"name": "frontend-design",
"description": "Frontend design skill for UI/UX implementation",
"author": {
"name": "Prithvi Rajasekaran, Alexander Bricken",
"email": "prithvi@anthropic.com, alexander@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
}
}

View File

@@ -0,0 +1,20 @@
# gopls-lsp
Go language server for Claude Code, providing code intelligence, refactoring, and analysis.
## Supported Extensions
`.go`
## Installation
Install gopls using the Go toolchain:
```bash
go install golang.org/x/tools/gopls@latest
```
Make sure `$GOPATH/bin` (or `$HOME/go/bin`) is in your PATH.
## More Information
- [gopls Documentation](https://pkg.go.dev/golang.org/x/tools/gopls)
- [GitHub Repository](https://github.com/golang/tools/tree/master/gopls)

View File

@@ -2,7 +2,7 @@
"name": "hookify",
"description": "Easily create hooks to prevent unwanted behaviors by analyzing conversation patterns",
"author": {
"name": "Daisy Hollman",
"email": "daisy@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
}
}

View File

@@ -0,0 +1,33 @@
# jdtls-lsp
Java language server (Eclipse JDT.LS) for Claude Code, providing code intelligence and refactoring.
## Supported Extensions
`.java`
## Installation
### Via Homebrew (macOS)
```bash
brew install jdtls
```
### Via package manager (Linux)
```bash
# Arch Linux (AUR)
yay -S jdtls
# Other distros: manual installation required
```
### Manual Installation
1. Download from [Eclipse JDT.LS releases](https://download.eclipse.org/jdtls/snapshots/)
2. Extract to a directory (e.g., `~/.local/share/jdtls`)
3. Create a wrapper script named `jdtls` in your PATH
## Requirements
- Java 17 or later (JDK, not just JRE)
## More Information
- [Eclipse JDT.LS GitHub](https://github.com/eclipse-jdtls/eclipse.jdt.ls)
- [VSCode Java Extension](https://github.com/redhat-developer/vscode-java) (uses JDT.LS)

View File

@@ -2,7 +2,7 @@
"name": "learning-output-style",
"description": "Interactive learning mode that requests meaningful code contributions at decision points (mimics the unshipped Learning output style)",
"author": {
"name": "Boris Cherny",
"email": "boris@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
}
}

32
plugins/lua-lsp/README.md Normal file
View File

@@ -0,0 +1,32 @@
# lua-lsp
Lua language server for Claude Code, providing code intelligence and diagnostics.
## Supported Extensions
`.lua`
## Installation
### Via Homebrew (macOS)
```bash
brew install lua-language-server
```
### Via package manager (Linux)
```bash
# Ubuntu/Debian (via snap)
sudo snap install lua-language-server --classic
# Arch Linux
sudo pacman -S lua-language-server
# Fedora
sudo dnf install lua-language-server
```
### Manual Installation
Download pre-built binaries from the [releases page](https://github.com/LuaLS/lua-language-server/releases).
## More Information
- [Lua Language Server GitHub](https://github.com/LuaLS/lua-language-server)
- [Documentation](https://luals.github.io/)

24
plugins/php-lsp/README.md Normal file
View File

@@ -0,0 +1,24 @@
# php-lsp
PHP language server (Intelephense) for Claude Code, providing code intelligence and diagnostics.
## Supported Extensions
`.php`
## Installation
Install Intelephense globally via npm:
```bash
npm install -g intelephense
```
Or with yarn:
```bash
yarn global add intelephense
```
## More Information
- [Intelephense Website](https://intelephense.com/)
- [Intelephense on npm](https://www.npmjs.com/package/intelephense)

View File

@@ -2,7 +2,7 @@
"name": "pr-review-toolkit",
"description": "Comprehensive PR review agents specializing in comments, tests, error handling, type design, code quality, and code simplification",
"author": {
"name": "Daisy",
"email": "daisy@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
}
}

View File

@@ -0,0 +1,31 @@
# pyright-lsp
Python language server (Pyright) for Claude Code, providing static type checking and code intelligence.
## Supported Extensions
`.py`, `.pyi`
## Installation
Install Pyright globally via npm:
```bash
npm install -g pyright
```
Or with pip:
```bash
pip install pyright
```
Or with pipx (recommended for CLI tools):
```bash
pipx install pyright
```
## More Information
- [Pyright on npm](https://www.npmjs.com/package/pyright)
- [Pyright on PyPI](https://pypi.org/project/pyright/)
- [GitHub Repository](https://github.com/microsoft/pyright)

View File

@@ -2,7 +2,7 @@
"name": "ralph-wiggum",
"description": "Implementation of the Ralph Wiggum technique - continuous self-referential AI loops for interactive iterative development. Run Claude in a while-true loop with the same prompt until task completion.",
"author": {
"name": "Daisy Hollman",
"email": "daisy@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
}
}

View File

@@ -0,0 +1,34 @@
# rust-analyzer-lsp
Rust language server for Claude Code, providing code intelligence and analysis.
## Supported Extensions
`.rs`
## Installation
### Via rustup (recommended)
```bash
rustup component add rust-analyzer
```
### Via Homebrew (macOS)
```bash
brew install rust-analyzer
```
### Via package manager (Linux)
```bash
# Ubuntu/Debian
sudo apt install rust-analyzer
# Arch Linux
sudo pacman -S rust-analyzer
```
### Manual download
Download pre-built binaries from the [releases page](https://github.com/rust-lang/rust-analyzer/releases).
## More Information
- [rust-analyzer Website](https://rust-analyzer.github.io/)
- [GitHub Repository](https://github.com/rust-lang/rust-analyzer)

View File

@@ -2,7 +2,7 @@
"name": "security-guidance",
"description": "Security reminder hook that warns about potential security issues when editing files, including command injection, XSS, and unsafe code patterns",
"author": {
"name": "David Dworken",
"email": "dworken@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
}
}

View File

@@ -0,0 +1,25 @@
# swift-lsp
Swift language server (SourceKit-LSP) for Claude Code, providing code intelligence for Swift projects.
## Supported Extensions
`.swift`
## Installation
SourceKit-LSP is included with the Swift toolchain.
### macOS
Install Xcode from the App Store, or install Swift via:
```bash
brew install swift
```
### Linux
Download and install Swift from [swift.org](https://www.swift.org/download/).
After installation, `sourcekit-lsp` should be available in your PATH.
## More Information
- [SourceKit-LSP GitHub](https://github.com/apple/sourcekit-lsp)
- [Swift.org](https://www.swift.org/)

View File

@@ -0,0 +1,24 @@
# typescript-lsp
TypeScript/JavaScript language server for Claude Code, providing code intelligence features like go-to-definition, find references, and error checking.
## Supported Extensions
`.ts`, `.tsx`, `.js`, `.jsx`, `.mts`, `.cts`, `.mjs`, `.cjs`
## Installation
Install the TypeScript language server globally via npm:
```bash
npm install -g typescript-language-server typescript
```
Or with yarn:
```bash
yarn global add typescript-language-server typescript
```
## More Information
- [typescript-language-server on npm](https://www.npmjs.com/package/typescript-language-server)
- [GitHub Repository](https://github.com/typescript-language-server/typescript-language-server)