Compare commits

..

25 Commits

Author SHA1 Message Date
Claude
4a369eb2ff Add superpowers plugin to marketplace
This plugin teaches Claude brainstorming, subagent driven development
with built in code review, systematic debugging, and red/green TDD.
Additionally, it teaches Claude how to author and test new skills.
2026-01-07 02:20:45 +00:00
Noah Zweben
76334d1f67 Add write permissions for external PR workflow (#143)
* Add write permissions for external PR workflow

* Use pulls.createReview instead of issues.createComment

* Revert to issues.createComment with proper permissions
2026-01-06 17:09:02 -08:00
Noah Zweben
44328beed4 Rename ralph-wiggum plugin to ralph-loop per legal guidance (#142)
- Rename plugin from "ralph-wiggum" to "ralph-loop" to avoid trademark concerns
- Update all internal references to use "Ralph Loop" as the prominent name
- Keep explanatory text noting it "implements the Ralph Wiggum technique" (allowed)
- Rename plugin directory from plugins/ralph-wiggum to plugins/ralph-loop
- Update marketplace.json with new plugin name and source path
- Update plugin-dev documentation references

This change follows legal's recommendation to replace "Wiggum" with "Loop"
in the plugin name while still explaining the technique origin.

Slack thread: https://anthropic.slack.com/archives/C09KU300P7F/p1767741142753959

Co-authored-by: Claude <noreply@anthropic.com>
2026-01-06 15:22:54 -08:00
Noah Zweben
6703e9f512 Add workflow to auto-close external PRs (#140)
* Add workflow to auto-close external PRs

* Update PR comment wording

* Add toggle to disable external PR check
2026-01-06 15:06:28 -08:00
Anthony Morris
bf48ae6c75 fix(ralph-wiggum): add :* to allowed-tools pattern to permit arguments (#138)
The allowed-tools pattern was missing :* suffix, causing permission check
failures when arguments were passed to the setup script via ```! block.

Fixes anthropics/claude-code#16398
2026-01-06 13:46:06 -08:00
Noah Zweben
883f2ba69e Add Pinecone vector database plugin to marketplace (#133)
Add new community plugin for Pinecone vector database integration,
enabling developers to manage vector indexes, query data, and build
RAG applications with Claude Code.

Co-authored-by: Claude <noreply@anthropic.com>
2026-01-06 11:36:19 -08:00
Noah Zweben
dbc4a7733c Add README and setup documentation for Greptile plugin (#122)
Claude-Generated-By: Claude Code (cli/claude-opus-4-5=100%)
Claude-Steers: 2
Claude-Permission-Prompts: 4
Claude-Escapes: 0
2026-01-05 21:15:35 -08:00
Anthony Morris
15b07b46da Merge pull request #114 from anthropics/fix/ralph-wiggum-newline-error
fix(ralph-wiggum): move multi-line bash from command to setup script
2026-01-04 23:16:39 -08:00
Daisy S. Hollman
6d3752c000 Merge pull request #39 from anthropics/daisy/plugins/fix-hookify-imports
Fix hookify plugin import error: No module named 'hookify'
2025-12-18 20:29:39 -08:00
Daisy Hollman
5f2db35c65 Fix hookify plugin import error: No module named 'hookify'
The hook scripts used absolute imports like `from hookify.core.config_loader`
but when installed, the plugin lives in a cache directory with a hash name,
not in a directory named `hookify/`. Python couldn't resolve the package.

Changed to local imports (`from core.X`) which work because PLUGIN_ROOT
is added to sys.path. Also simplified the sys.path setup.

Fixes: https://github.com/anthropics/claude-code/issues/14267

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

Co-Authored-By: Claude <noreply@anthropic.com>
2025-12-19 02:54:38 +00:00
Daisy S. Hollman
4bab8d0f50 Merge pull request #38 from anthropics/daisy/plugins/add-lsp-plugins
Add LSP plugins with inline lspServers configuration
2025-12-18 17:59:19 -08:00
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
Noah Zweben MacBook
ef7ceef127 fixed readme 2025-11-20 14:28:47 -08:00
Noah Zweben MacBook
6ba8050494 updated readme 2025-11-20 14:26:30 -08:00
Noah Zweben MacBook
0f1535a523 simplified example agent 2025-11-20 14:23:57 -08:00
Noah Zweben MacBook
66a98580ee Merge branch 'noahz/initial_scaffold' 2025-11-20 13:49:51 -08:00
Noah Zweben MacBook
c7fb157236 remove readme from external plugins 2025-11-20 13:49:05 -08:00
Noah Zweben MacBook
cecebb12fb added readme 2025-11-20 13:12:07 -08:00
93 changed files with 1015 additions and 882 deletions

View File

@@ -1,241 +1,527 @@
{
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
"name": "claude-code-marketplace",
"version": "1.0.0",
"description": "Official marketplace for high-quality Claude Code extensions including development tools, productivity plugins, and MCP integrations",
"name": "claude-plugins-official",
"description": "Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations",
"owner": {
"name": "Anthropic",
"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"
"category": "development",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/plugins/agent-sdk-dev"
},
{
"name": "pr-review-toolkit",
"description": "Comprehensive PR review agents specializing in comments, tests, error handling, type design, code quality, and code simplification",
"version": "1.0.0",
"author": {
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/pr-review-toolkit",
"category": "productivity"
"category": "productivity",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/plugins/pr-review-toolkit"
},
{
"name": "commit-commands",
"description": "Commands for git commit workflows including commit, push, and PR creation",
"version": "1.0.0",
"author": {
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/commit-commands",
"category": "productivity"
"category": "productivity",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/plugins/commit-commands"
},
{
"name": "feature-dev",
"description": "Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review",
"version": "1.0.0",
"author": {
"name": "Siddharth Bidasaria",
"email": "sbidasaria@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/feature-dev",
"category": "development"
"category": "development",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/plugins/feature-dev"
},
{
"name": "security-guidance",
"description": "Security reminder hook that warns about potential security issues when editing files, including command injection, XSS, and unsafe code patterns",
"version": "1.0.0",
"author": {
"name": "David Dworken",
"email": "dworken@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/security-guidance",
"category": "security"
"category": "security",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/plugins/security-guidance"
},
{
"name": "code-review",
"description": "Automated code review for pull requests using multiple specialized agents with confidence-based scoring to filter false positives",
"version": "1.0.0",
"author": {
"name": "Boris Cherny",
"email": "boris@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/code-review",
"category": "productivity"
"category": "productivity",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/plugins/code-review"
},
{
"name": "explanatory-output-style",
"description": "Adds educational insights about implementation choices and codebase patterns (mimics the deprecated Explanatory output style)",
"version": "1.0.0",
"author": {
"name": "Dickson Tsai",
"email": "dickson@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/explanatory-output-style",
"category": "learning"
"category": "learning",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/plugins/explanatory-output-style"
},
{
"name": "learning-output-style",
"description": "Interactive learning mode that requests meaningful code contributions at decision points (mimics the unshipped Learning output style)",
"version": "1.0.0",
"author": {
"name": "Boris Cherny",
"email": "boris@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/learning-output-style",
"category": "learning"
"category": "learning",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/plugins/learning-output-style"
},
{
"name": "frontend-design",
"description": "Create distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics.",
"version": "1.0.0",
"author": {
"name": "Prithvi Rajasekaran & Alexander Bricken",
"email": "prithvi@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/frontend-design",
"category": "development"
"category": "development",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/plugins/frontend-design"
},
{
"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.",
"version": "1.0.0",
"name": "ralph-loop",
"description": "Interactive self-referential AI loops for iterative development, implementing the Ralph Wiggum technique. 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"
"source": "./plugins/ralph-loop",
"category": "development",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/plugins/ralph-loop"
},
{
"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.",
"version": "0.1.0",
"author": {
"name": "Daisy Hollman",
"email": "daisy@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/hookify",
"category": "productivity"
"category": "productivity",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/plugins/hookify"
},
{
"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.",
"version": "0.1.0",
"author": {
"name": "Daisy Hollman",
"email": "daisy@anthropic.com"
"name": "Anthropic",
"email": "support@anthropic.com"
},
"source": "./plugins/plugin-dev",
"category": "development"
"category": "development",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/plugins/plugin-dev"
},
{
"name": "greptile",
"description": "AI-powered codebase search and understanding. Query your repositories using natural language to find relevant code, understand dependencies, and get contextual answers about your codebase architecture.",
"category": "development",
"source": "./external_plugins/greptile"
"source": "./external_plugins/greptile",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/external_plugins/greptile"
},
{
"name": "serena",
"description": "Semantic code analysis MCP server providing intelligent code understanding, refactoring suggestions, and codebase navigation through language server protocol integration.",
"category": "development",
"source": "./external_plugins/serena"
"source": "./external_plugins/serena",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/external_plugins/serena",
"tags": ["community-managed"]
},
{
"name": "playwright",
"description": "Browser automation and end-to-end testing MCP server by Microsoft. Enables Claude to interact with web pages, take screenshots, fill forms, click elements, and perform automated browser testing workflows.",
"category": "testing",
"source": "./external_plugins/playwright"
"source": "./external_plugins/playwright",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/external_plugins/playwright"
},
{
"name": "github",
"description": "Official GitHub MCP server for repository management. Create issues, manage pull requests, review code, search repositories, and interact with GitHub's full API directly from Claude Code.",
"category": "productivity",
"source": "./external_plugins/github"
"source": "./external_plugins/github",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/external_plugins/github"
},
{
"name": "supabase",
"description": "Supabase MCP integration for database operations, authentication, storage, and real-time subscriptions. Manage your Supabase projects, run SQL queries, and interact with your backend directly.",
"category": "database",
"source": "./external_plugins/supabase"
"source": "./external_plugins/supabase",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/external_plugins/supabase"
},
{
"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"
"source": {
"source": "url",
"url": "https://github.com/atlassian/atlassian-mcp-server.git"
},
"homepage": "https://github.com/atlassian/atlassian-mcp-server"
},
{
"name": "laravel-boost",
"description": "Laravel development toolkit MCP server. Provides intelligent assistance for Laravel applications including Artisan commands, Eloquent queries, routing, migrations, and framework-specific code generation.",
"category": "development",
"source": "./external_plugins/laravel-boost"
"source": "./external_plugins/laravel-boost",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/external_plugins/laravel-boost"
},
{
"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"
"source": {
"source": "url",
"url": "https://github.com/figma/mcp-server-guide.git"
},
"homepage": "https://github.com/figma/mcp-server-guide"
},
{
"name": "asana",
"description": "Asana project management integration. Create and manage tasks, search projects, update assignments, track progress, and integrate your development workflow with Asana's work management platform.",
"category": "productivity",
"source": "./external_plugins/asana"
"source": "./external_plugins/asana",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/external_plugins/asana"
},
{
"name": "linear",
"description": "Linear issue tracking integration. Create issues, manage projects, update statuses, search across workspaces, and streamline your software development workflow with Linear's modern issue tracker.",
"category": "productivity",
"source": "./external_plugins/linear"
"source": "./external_plugins/linear",
"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"
"source": {
"source": "url",
"url": "https://github.com/makenotion/claude-code-notion-plugin.git"
},
"homepage": "https://github.com/makenotion/claude-code-notion-plugin"
},
{
"name": "gitlab",
"description": "GitLab DevOps platform integration. Manage repositories, merge requests, CI/CD pipelines, issues, and wikis. Full access to GitLab's comprehensive DevOps lifecycle tools.",
"category": "productivity",
"source": "./external_plugins/gitlab"
"source": "./external_plugins/gitlab",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/external_plugins/gitlab"
},
{
"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"
"source": {
"source": "url",
"url": "https://github.com/getsentry/sentry-for-claude.git"
},
"homepage": "https://github.com/getsentry/sentry-for-claude/tree/main"
},
{
"name": "slack",
"description": "Slack workspace integration. Search messages, access channels, read threads, and stay connected with your team's communications while coding. Find relevant discussions and context quickly.",
"category": "productivity",
"source": "./external_plugins/slack"
"source": "./external_plugins/slack",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/external_plugins/slack"
},
{
"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"
"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",
"description": "Google Firebase MCP integration. Manage Firestore databases, authentication, cloud functions, hosting, and storage. Build and manage your Firebase backend directly from your development workflow.",
"category": "database",
"source": "./external_plugins/firebase"
"source": "./external_plugins/firebase",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/external_plugins/firebase"
},
{
"name": "context7",
"description": "Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.",
"category": "development",
"source": "./external_plugins/context7"
"source": "./external_plugins/context7",
"homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/external_plugins/context7",
"tags": ["community-managed"]
},
{
"name": "pinecone",
"description": "Pinecone vector database integration. Streamline your Pinecone development with powerful tools for managing vector indexes, querying data, and rapid prototyping. Use slash commands like /quickstart to generate AGENTS.md files and initialize Python projects and /query to quickly explore indexes. Access the Pinecone MCP server for creating, describing, upserting and querying indexes with Claude. Perfect for developers building semantic search, RAG applications, recommendation systems, and other vector-based applications with Pinecone.",
"category": "database",
"source": {
"source": "url",
"url": "https://github.com/pinecone-io/pinecone-claude-code-plugin.git"
},
"homepage": "https://github.com/pinecone-io/pinecone-claude-code-plugin"
},
{
"name": "superpowers",
"description": "Superpowers teaches Claude brainstorming, subagent driven development with built in code review, systematic debugging, and red/green TDD. Additionally, it teaches Claude how to author and test new skills.",
"category": "development",
"source": {
"source": "url",
"url": "https://github.com/obra/superpowers.git"
},
"homepage": "https://github.com/obra/superpowers"
}
]
}

View File

@@ -0,0 +1,47 @@
name: Close External PRs
on:
pull_request_target:
types: [opened]
permissions:
pull-requests: write
issues: write
jobs:
check-membership:
if: vars.DISABLE_EXTERNAL_PR_CHECK != 'true'
runs-on: ubuntu-latest
steps:
- name: Check if author is org member
uses: actions/github-script@v7
with:
script: |
const org = 'anthropics';
const author = context.payload.pull_request.user.login;
try {
await github.rest.orgs.checkMembershipForUser({
org: org,
username: author
});
console.log(`${author} is an org member, allowing PR`);
} catch (e) {
if (e.status === 404) {
await github.rest.issues.createComment({
owner: context.repo.owner,
repo: context.repo.repo,
issue_number: context.payload.pull_request.number,
body: `Thanks for your interest! This repo only accepts contributions from Anthropic team members. If you'd like to submit a plugin to the marketplace, please submit your plugin [here](https://docs.google.com/forms/d/e/1FAIpQLSdeFthxvjOXUjxg1i3KrOOkEPDJtn71XC-KjmQlxNP63xYydg/viewform).`
});
await github.rest.pulls.update({
owner: context.repo.owner,
repo: context.repo.repo,
pull_number: context.payload.pull_request.number,
state: 'closed'
});
console.log(`Closed PR from external contributor: ${author}`);
}
}

2
.gitignore vendored Normal file
View File

@@ -0,0 +1,2 @@
*.DS_Store
.claude/

47
README.md Normal file
View File

@@ -0,0 +1,47 @@
# Claude Code Plugins Directory
A curated directory of high-quality plugins for Claude Code.
> **⚠️ Important:** Make sure you trust a plugin before installing, updating, or using it. Anthropic does not control what MCP servers, files, or other software are included in plugins and cannot verify that they will work as intended or that they won't change. See each plugin's homepage for more information.
## Structure
- **`/plugins`** - Internal plugins developed and maintained by Anthropic
- **`/external_plugins`** - Third-party plugins from partners and the community
## Installation
Plugins can be installed directly from this marketplace via Claude Code's plugin system.
To install, run `/plugin install {plugin-name}@claude-plugin-directory`
or browse for the plugin in `/plugin > Discover`
## Contributing
### Internal Plugins
Internal plugins are developed by Anthropic team members. See `/plugins/example-plugin` for a reference implementation.
### External Plugins
Third-party partners can submit plugins for inclusion in the marketplace. External plugins must meet quality and security standards for approval.
## Plugin Structure
Each plugin follows a standard structure:
```
plugin-name/
├── .claude-plugin/
│ └── plugin.json # Plugin metadata (required)
├── .mcp.json # MCP server configuration (optional)
├── commands/ # Slash commands (optional)
├── agents/ # Agent definitions (optional)
├── skills/ # Skill definitions (optional)
└── README.md # Documentation
```
## Documentation
For more information on developing Claude Code plugins, see the [official documentation](https://code.claude.com/docs/en/plugins).

View File

@@ -1,7 +1,6 @@
{
"name": "asana",
"description": "Asana project management integration. Create and manage tasks, search projects, update assignments, track progress, and integrate your development workflow with Asana's work management platform.",
"version": "1.0.0",
"author": {
"name": "Asana"
}

View File

@@ -1,15 +0,0 @@
# Asana Plugin
Asana project management integration for Claude Code.
## What It Does
Create and manage tasks, search projects, update assignments, track progress, and integrate your development workflow with Asana's work management platform.
## Setup
Authentication is handled automatically via OAuth when you first use the plugin. You will be prompted to authorize access to your Asana account.
## Learn More
See [Asana Connector](https://www.claude.com/connectors/asana) for more information.

View File

@@ -1,8 +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.",
"version": "1.0.0",
"author": {
"name": "Atlassian"
}
}

View File

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

View File

@@ -1,15 +0,0 @@
# Atlassian Plugin
Atlassian integration (Jira & Confluence) for Claude Code.
## What It Does
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.
## Setup
Authentication is handled automatically via OAuth when you first use the plugin. You will be prompted to authorize access to your Atlassian account.
## Learn More
See [Atlassian Connector](https://www.claude.com/connectors/atlassian) for more information.

View File

@@ -1,7 +1,6 @@
{
"name": "context7",
"description": "Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.",
"version": "1.0.0",
"author": {
"name": "Upstash"
}

View File

@@ -1,41 +0,0 @@
# Context7 Plugin
Upstash Context7 MCP server for Claude Code.
## What It Does
Pull up-to-date, version-specific documentation and code examples directly from source repositories into your LLM context. Add "use context7" to prompts to fetch relevant documentation.
## Prerequisites
- Node.js >= v18.0.0
## Optional: API Key for Higher Rate Limits
For higher rate limits and private repository access, get an API key and configure:
```json
{
"context7": {
"command": "npx",
"args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]
}
}
```
Or use the remote server:
```json
{
"context7": {
"type": "http",
"url": "https://mcp.context7.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
```
## Learn More
See [Context7 GitHub](https://github.com/upstash/context7) for detailed documentation.

View File

@@ -1,8 +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.",
"version": "1.0.0",
"author": {
"name": "Figma"
}
}

View File

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

View File

@@ -1,15 +0,0 @@
# Figma Plugin
Figma design platform integration for Claude Code.
## What It Does
Access design files, extract component information, read design tokens, and translate designs into code. Bridge the gap between design and development workflows.
## Setup
Authentication is handled automatically via OAuth when you first use the plugin. You will be prompted to authorize access to your Figma account.
## Learn More
See [Figma Connector](https://www.claude.com/connectors/figma) for more information.

View File

@@ -1,7 +1,6 @@
{
"name": "firebase",
"description": "Google Firebase MCP integration. Manage Firestore databases, authentication, cloud functions, hosting, and storage. Build and manage your Firebase backend directly from your development workflow.",
"version": "1.0.0",
"author": {
"name": "Google"
}

View File

@@ -1,32 +0,0 @@
# Firebase Plugin
Google Firebase MCP integration for Claude Code.
## What It Does
Manage Firestore databases, authentication, cloud functions, hosting, and storage. Build and manage your Firebase backend directly from your development workflow.
## Prerequisites
- Node.js installed
- Firebase CLI credentials (logged in via `firebase login` or Application Default Credentials)
## Optional Configuration
Add arguments to customize behavior:
- `--dir ABSOLUTE_DIR_PATH` - Set project context directory
- `--only FEATURE_1,FEATURE_2` - Limit exposed tools (comma-separated)
Example with options:
```json
{
"firebase": {
"command": "npx",
"args": ["-y", "firebase-tools@latest", "mcp", "--dir", "/path/to/project", "--only", "auth,firestore"]
}
}
```
## Learn More
See [Firebase MCP Documentation](https://firebase.google.com/docs/ai-assistance/mcp-server) for detailed setup instructions.

View File

@@ -1,7 +1,6 @@
{
"name": "github",
"description": "Official GitHub MCP server for repository management. Create issues, manage pull requests, review code, search repositories, and interact with GitHub's full API directly from Claude Code.",
"version": "1.0.0",
"author": {
"name": "GitHub"
}

View File

@@ -1,38 +0,0 @@
# GitHub Plugin
Official GitHub MCP server for Claude Code.
## What It Does
Create issues, manage pull requests, review code, search repositories, and interact with GitHub's full API directly from Claude Code.
## Setup
1. Create a GitHub Personal Access Token with appropriate scopes
2. Set the environment variable:
```bash
export GITHUB_PERSONAL_ACCESS_TOKEN=your-token-here
```
## Required Environment Variables
- `GITHUB_PERSONAL_ACCESS_TOKEN` - Your GitHub PAT with appropriate scopes
## Alternative: Docker Setup
For local server deployment:
```json
{
"github": {
"command": "docker",
"args": ["run", "-i", "--rm", "-e", "GITHUB_PERSONAL_ACCESS_TOKEN", "ghcr.io/github/github-mcp-server"],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_PERSONAL_ACCESS_TOKEN}"
}
}
}
```
## Learn More
See [GitHub MCP Server](https://github.com/github/github-mcp-server) for detailed documentation.

View File

@@ -1,7 +1,6 @@
{
"name": "gitlab",
"description": "GitLab DevOps platform integration. Manage repositories, merge requests, CI/CD pipelines, issues, and wikis. Full access to GitLab's comprehensive DevOps lifecycle tools.",
"version": "1.0.0",
"author": {
"name": "GitLab"
}

View File

@@ -1,39 +0,0 @@
# GitLab Plugin
GitLab DevOps platform integration for Claude Code.
## What It Does
Manage repositories, merge requests, CI/CD pipelines, issues, and wikis. Full access to GitLab's comprehensive DevOps lifecycle tools.
## Setup
The default configuration uses GitLab.com. For self-hosted GitLab instances, modify the URL in `.mcp.json`:
```json
{
"gitlab": {
"type": "http",
"url": "https://your-gitlab-instance.com/api/v4/mcp"
}
}
```
## Prerequisites
- Node.js 20+ (for stdio transport alternative)
## Alternative: stdio Transport
```json
{
"gitlab": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://gitlab.com/api/v4/mcp"]
}
}
```
## Learn More
See [GitLab MCP Documentation](https://docs.gitlab.com/user/gitlab_duo/model_context_protocol/mcp_server/) for detailed setup instructions.

View File

@@ -1,8 +1,10 @@
{
"name": "greptile",
"description": "AI-powered codebase search and understanding. Query your repositories using natural language to find relevant code, understand dependencies, and get contextual answers about your codebase architecture.",
"version": "1.0.0",
"description": "AI code review agent for GitHub and GitLab. View and resolve Greptile's PR review comments directly from Claude Code.",
"author": {
"name": "Greptile"
}
"name": "Greptile",
"url": "https://greptile.com"
},
"homepage": "https://greptile.com/docs",
"keywords": ["code-review", "pull-requests", "github", "gitlab", "ai"]
}

View File

@@ -1,23 +1,57 @@
# Greptile Plugin
# Greptile
AI-powered codebase search and understanding for Claude Code.
## What It Does
Greptile enables natural language queries across your repositories to find relevant code, understand dependencies, and get contextual answers about your codebase architecture.
[Greptile](https://greptile.com) is an AI code review agent for GitHub and GitLab that automatically reviews pull requests. This plugin connects Claude Code to your Greptile account, letting you view and resolve Greptile's review comments directly from your terminal.
## Setup
1. Get your API key from [app.greptile.com](https://app.greptile.com)
2. Set the environment variable:
```bash
export GREPTILE_API_KEY=your-api-key-here
```
### 1. Create a Greptile Account
## Required Environment Variables
Sign up at [greptile.com](https://greptile.com) and connect your GitHub or GitLab repositories.
- `GREPTILE_API_KEY` - Your Greptile API key
### 2. Get Your API Key
## Learn More
1. Go to [API Settings](https://app.greptile.com/settings/api)
2. Generate a new API key
3. Copy the key
See [Greptile MCP Documentation](https://www.greptile.com/docs/mcp/setup-ides) for detailed setup instructions.
### 3. Set Environment Variable
Add to your shell profile (`.bashrc`, `.zshrc`, etc.):
```bash
export GREPTILE_API_KEY="your-api-key-here"
```
Then reload your shell or run `source ~/.zshrc`.
## Available Tools
### Pull Request Tools
- `list_pull_requests` - List PRs with optional filtering by repo, branch, author, or state
- `get_merge_request` - Get detailed PR info including review analysis
- `list_merge_request_comments` - Get all comments on a PR with filtering options
### Code Review Tools
- `list_code_reviews` - List code reviews with optional filtering
- `get_code_review` - Get detailed code review information
- `trigger_code_review` - Start a new Greptile review on a PR
### Comment Search
- `search_greptile_comments` - Search across all Greptile review comments
### Custom Context Tools
- `list_custom_context` - List your organization's coding patterns and rules
- `get_custom_context` - Get details for a specific pattern
- `search_custom_context` - Search patterns by content
- `create_custom_context` - Create a new coding pattern
## Example Usage
Ask Claude Code to:
- "Show me Greptile's comments on my current PR and help me resolve them"
- "What issues did Greptile find on PR #123?"
- "Trigger a Greptile review on this branch"
## Documentation
For more information, visit [greptile.com/docs](https://greptile.com/docs).

View File

@@ -1,7 +1,6 @@
{
"name": "laravel-boost",
"description": "Laravel development toolkit MCP server. Provides intelligent assistance for Laravel applications including Artisan commands, Eloquent queries, routing, migrations, and framework-specific code generation.",
"version": "1.0.0",
"author": {
"name": "Laravel"
}

View File

@@ -1,26 +0,0 @@
# Laravel Boost Plugin
Laravel development toolkit MCP server for Claude Code.
## What It Does
Provides over 15 specialized tools for Laravel development including Artisan commands, Eloquent queries, routing, migrations, and framework-specific code generation.
## Prerequisites
- Laravel project with Boost installed
- PHP installed
## Setup
1. Install Laravel Boost in your project:
```bash
composer require laravel/boost
php artisan boost:install
```
2. The MCP server is automatically registered during installation
## Learn More
See [Laravel Boost GitHub](https://github.com/laravel/boost) for detailed documentation.

View File

@@ -1,7 +1,6 @@
{
"name": "linear",
"description": "Linear issue tracking integration. Create issues, manage projects, update statuses, search across workspaces, and streamline your software development workflow with Linear's modern issue tracker.",
"version": "1.0.0",
"author": {
"name": "Linear"
}

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,15 +0,0 @@
# Linear Plugin
Linear issue tracking integration for Claude Code.
## What It Does
Create issues, manage projects, update statuses, search across workspaces, and streamline your software development workflow with Linear's modern issue tracker.
## Setup
Authentication is handled automatically via OAuth when you first use the plugin. You will be prompted to authorize access to your Linear account.
## Learn More
See [Linear Connector](https://www.claude.com/connectors/linear) for more information.

View File

@@ -1,8 +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.",
"version": "1.0.0",
"author": {
"name": "Notion"
}
}

View File

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

View File

@@ -1,15 +0,0 @@
# Notion Plugin
Notion workspace integration for Claude Code.
## What It Does
Search pages, create and update documents, manage databases, and access your team's knowledge base directly from Claude Code for seamless documentation workflows.
## Setup
Authentication is handled automatically via OAuth when you first use the plugin. You will be prompted to authorize access to your Notion workspace.
## Learn More
See [Notion Connector](https://www.claude.com/connectors/notion) for more information.

View File

@@ -1,7 +1,6 @@
{
"name": "playwright",
"description": "Browser automation and end-to-end testing MCP server by Microsoft. Enables Claude to interact with web pages, take screenshots, fill forms, click elements, and perform automated browser testing workflows.",
"version": "1.0.0",
"author": {
"name": "Microsoft"
}

View File

@@ -1,22 +0,0 @@
# Playwright Plugin
Browser automation and end-to-end testing MCP server for Claude Code.
## What It Does
Enables Claude to interact with web pages, take screenshots, fill forms, click elements, and perform automated browser testing workflows.
## Prerequisites
- Node.js installed
## Optional Configuration
Add arguments to customize behavior:
- `--browser` - Specify browser type (chrome, firefox, webkit, msedge)
- `--headless` - Run in headless mode
- `--viewport-size` - Browser dimensions (e.g., "1280x720")
## Learn More
See [Playwright MCP GitHub](https://github.com/microsoft/playwright-mcp) for detailed documentation.

View File

@@ -1,8 +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.",
"version": "1.0.0",
"author": {
"name": "Sentry"
}
}

View File

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

View File

@@ -1,15 +0,0 @@
# Sentry Plugin
Sentry error monitoring integration for Claude Code.
## What It Does
Access error reports, analyze stack traces, search issues by fingerprint, and debug production errors directly from your development environment.
## Setup
Authentication is handled automatically via OAuth when you first use the plugin. You will be prompted to authorize access to your Sentry account.
## Learn More
See [Sentry Connector](https://www.claude.com/connectors/sentry) for more information.

View File

@@ -1,7 +1,6 @@
{
"name": "serena",
"description": "Semantic code analysis MCP server providing intelligent code understanding, refactoring suggestions, and codebase navigation through language server protocol integration.",
"version": "1.0.0",
"author": {
"name": "Oraios"
}

View File

@@ -1,22 +0,0 @@
# Serena Plugin
Semantic code analysis MCP server for Claude Code.
## What It Does
Serena provides intelligent code understanding, refactoring suggestions, and codebase navigation through language server protocol integration.
## Prerequisites
- Python with `uv` package manager installed
## Setup
The plugin automatically runs via `uvx`. Ensure you have `uv` installed:
```bash
pip install uv
```
## Learn More
See [Serena GitHub Repository](https://github.com/oraios/serena) for detailed documentation.

View File

@@ -1,7 +1,6 @@
{
"name": "slack",
"description": "Slack workspace integration. Search messages, access channels, read threads, and stay connected with your team's communications while coding. Find relevant discussions and context quickly.",
"version": "1.0.0",
"author": {
"name": "Slack"
}

View File

@@ -1,15 +0,0 @@
# Slack Plugin
Slack workspace integration for Claude Code.
## What It Does
Search messages, access channels, read threads, and stay connected with your team's communications while coding. Find relevant discussions and context quickly.
## Setup
Authentication is handled automatically via OAuth when you first use the plugin. You will be prompted to authorize access to your Slack workspace.
## Learn More
See [Slack Connector](https://www.claude.com/connectors/slack) for more information.

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 +1,6 @@
{
"name": "supabase",
"description": "Supabase MCP integration for database operations, authentication, storage, and real-time subscriptions. Manage your Supabase projects, run SQL queries, and interact with your backend directly.",
"version": "1.0.0",
"author": {
"name": "Supabase"
}

View File

@@ -1,21 +0,0 @@
# Supabase Plugin
Supabase MCP integration for Claude Code.
## What It Does
Manage your Supabase projects, run SQL queries, handle authentication, storage, and real-time subscriptions directly from Claude Code.
## Setup
Authentication is handled automatically via dynamic client registration in most cases.
## Optional: CI Environment Configuration
For CI environments, set these environment variables:
- `SUPABASE_PROJECT_REF` - Your Supabase project reference
- `SUPABASE_ACCESS_TOKEN` - Personal access token with appropriate scopes
## Learn More
See [Supabase MCP Documentation](https://supabase.com/docs/guides/getting-started/mcp) for detailed setup instructions.

View File

@@ -1,8 +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.",
"version": "1.0.0",
"author": {
"name": "Vercel"
}
}

View File

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

View File

@@ -1,15 +0,0 @@
# Vercel Plugin
Vercel deployment platform integration for Claude Code.
## What It Does
Manage deployments, check build status, access logs, configure domains, and control your frontend infrastructure directly from Claude Code.
## Setup
Authentication is handled automatically via OAuth when you first use the plugin. You will be prompted to authorize access to your Vercel account.
## Learn More
See [Vercel Connector](https://www.claude.com/connectors) for more information.

View File

@@ -1,103 +0,0 @@
# Claude Code Plugins
This directory contains some official Claude Code plugins that extend functionality through custom commands, agents, and workflows. These are examples of what's possible with the Claude Code plugin system—many more plugins are available through community marketplaces.
## What are Claude Code Plugins?
Claude Code plugins are extensions that enhance Claude Code with custom slash commands, specialized agents, hooks, and MCP servers. Plugins can be shared across projects and teams, providing consistent tooling and workflows.
Learn more in the [official plugins documentation](https://docs.claude.com/en/docs/claude-code/plugins).
## Plugins in This Directory
### [agent-sdk-dev](./agent-sdk-dev/)
**Claude Agent SDK Development Plugin**
Streamlines the development of Claude Agent SDK applications with scaffolding commands and verification agents.
- **Command**: `/new-sdk-app` - Interactive setup for new Agent SDK projects
- **Agents**: `agent-sdk-verifier-py` and `agent-sdk-verifier-ts` - Validate SDK applications against best practices
- **Use case**: Creating and verifying Claude Agent SDK applications in Python or TypeScript
### [commit-commands](./commit-commands/)
**Git Workflow Automation Plugin**
Simplifies common git operations with streamlined commands for committing, pushing, and creating pull requests.
- **Commands**:
- `/commit` - Create a git commit with appropriate message
- `/commit-push-pr` - Commit, push, and create a PR in one command
- `/clean_gone` - Clean up stale local branches marked as [gone]
- **Use case**: Faster git workflows with less context switching
### [code-review](./code-review/)
**Automated Pull Request Code Review Plugin**
Provides automated code review for pull requests using multiple specialized agents with confidence-based scoring to filter false positives.
- **Command**:
- `/code-review` - Automated PR review workflow
- **Use case**: Automated code review on pull requests with high-confidence issue detection (threshold ≥80)
### [feature-dev](./feature-dev/)
**Comprehensive Feature Development Workflow Plugin**
Provides a structured 7-phase approach to feature development with specialized agents for exploration, architecture, and review.
- **Command**: `/feature-dev` - Guided feature development workflow
- **Agents**:
- `code-explorer` - Deeply analyzes existing codebase features
- `code-architect` - Designs feature architectures and implementation blueprints
- `code-reviewer` - Reviews code for bugs, quality issues, and project conventions
- **Use case**: Building new features with systematic codebase understanding and quality assurance
## Installation
These plugins are included in the Claude Code repository. To use them in your own projects:
1. Install Claude Code globally:
```bash
npm install -g @anthropic-ai/claude-code
```
2. Navigate to your project and run Claude Code:
```bash
claude
```
3. Use the `/plugin` command to install plugins from marketplaces, or configure them in your project's `.claude/settings.json`.
For detailed plugin installation and configuration, see the [official documentation](https://docs.claude.com/en/docs/claude-code/plugins).
## Plugin Structure
Each plugin follows the standard Claude Code plugin structure:
```
plugin-name/
├── .claude-plugin/
│ └── plugin.json # Plugin metadata
├── commands/ # Slash commands (optional)
├── agents/ # Specialized agents (optional)
└── README.md # Plugin documentation
```
## Contributing
When adding new plugins to this directory:
1. Follow the standard plugin structure
2. Include a comprehensive README.md
3. Add plugin metadata in `.claude-plugin/plugin.json`
4. Document all commands and agents
5. Provide usage examples
## Learn More
- [Claude Code Documentation](https://docs.claude.com/en/docs/claude-code/overview)
- [Plugin System Documentation](https://docs.claude.com/en/docs/claude-code/plugins)
- [Agent SDK Documentation](https://docs.claude.com/en/api/agent-sdk/overview)

View File

@@ -1,9 +1,8 @@
{
"name": "agent-sdk-dev",
"description": "Claude Agent SDK Development Plugin",
"version": "1.0.0",
"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

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

View File

@@ -1,7 +1,6 @@
{
"name": "commit-commands",
"description": "Streamline your git workflow with simple commands for committing, pushing, and creating pull requests",
"version": "1.0.0",
"author": {
"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

@@ -1,9 +1,8 @@
{
"name": "example-plugin",
"version": "1.0.0",
"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

@@ -11,8 +11,6 @@ example-plugin/
├── .mcp.json # MCP server configuration
├── commands/
│ └── example-command.md # Slash command definition
├── agents/
│ └── example-agent.md # Agent definition
└── skills/
└── example-skill/
└── SKILL.md # Skill definition
@@ -32,20 +30,6 @@ allowed-tools: [Read, Glob, Grep]
---
```
### Agents (`agents/`)
Agents are spawned by Claude via the Task tool. Define them as markdown files:
```yaml
---
name: agent-name
description: When to use this agent
tools: Glob, Grep, Read, Write
model: sonnet
color: blue
---
```
### Skills (`skills/`)
Skills are model-invoked capabilities. Create a `SKILL.md` in a subdirectory:
@@ -71,12 +55,8 @@ Configure external tool integration via Model Context Protocol:
}
```
## Installation
Copy or symlink this plugin directory to your Claude Code plugins location.
## Usage
- `/example-command [args]` - Run the example slash command
- The example agent is available for Claude to spawn when relevant
- The example skill activates based on task context
- The example MCP activates based on task context

View File

@@ -1,57 +0,0 @@
---
name: example-agent
description: An example agent that demonstrates agent definition structure and frontmatter options. Use this agent when the user asks to perform example tasks or needs a template reference.
tools: Glob, Grep, Read, Write, Edit, Bash, WebFetch, WebSearch, TodoWrite
model: sonnet
color: blue
---
You are an example agent that demonstrates the agent definition format for Claude Code plugins.
## Agent Purpose
This agent serves as a template showing:
- Required and optional frontmatter fields
- Recommended prompt structure
- How to define agent capabilities and behavior
## Frontmatter Options Reference
Agents support these frontmatter fields:
- **name** (required): Agent identifier used in Task tool
- **description** (required): When to use this agent - Claude reads this to decide which agent to spawn
- **tools** (required): Comma-separated list of allowed tools
- **model** (optional): "haiku", "sonnet", or "opus" (defaults to parent model)
- **color** (optional): Terminal color for agent output (red, green, blue, yellow, magenta, cyan)
## Available Tools
Common tools to include:
- **Glob**: Find files by pattern
- **Grep**: Search file contents
- **Read**: Read file contents
- **Write**: Create new files
- **Edit**: Modify existing files
- **Bash**: Execute shell commands
- **WebFetch**: Fetch web content
- **WebSearch**: Search the web
- **TodoWrite**: Track task progress
- **NotebookRead**: Read Jupyter notebooks
- **LSP**: Language server operations
## Agent Behavior
When spawned, this agent should:
1. Understand the task from the prompt
2. Use available tools systematically
3. Report findings or complete the requested work
4. Return a clear summary to the parent conversation
## Best Practices
- Write clear, actionable descriptions so Claude knows when to spawn this agent
- Only include tools the agent actually needs
- Use appropriate model based on task complexity
- Structure prompts with clear sections and instructions

View File

@@ -1,9 +1,8 @@
{
"name": "explanatory-output-style",
"version": "1.0.0",
"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

@@ -1,9 +1,8 @@
{
"name": "feature-dev",
"version": "1.0.0",
"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

@@ -1,9 +1,8 @@
{
"name": "frontend-design",
"version": "1.0.0",
"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

@@ -1,9 +1,8 @@
{
"name": "hookify",
"version": "0.1.0",
"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

@@ -7,7 +7,7 @@ from functools import lru_cache
from typing import List, Dict, Any, Optional
# Import from local module
from hookify.core.config_loader import Rule, Condition
from core.config_loader import Rule, Condition
# Cache compiled regexes (max 128 patterns)
@@ -275,7 +275,7 @@ class RuleEngine:
# For testing
if __name__ == '__main__':
from hookify.core.config_loader import Condition, Rule
from core.config_loader import Condition, Rule
# Test rule evaluation
rule = Rule(

View File

@@ -9,18 +9,14 @@ import os
import sys
import json
# CRITICAL: Add plugin root to Python path for imports
# Add plugin root to Python path for imports
PLUGIN_ROOT = os.environ.get('CLAUDE_PLUGIN_ROOT')
if PLUGIN_ROOT:
parent_dir = os.path.dirname(PLUGIN_ROOT)
if parent_dir not in sys.path:
sys.path.insert(0, parent_dir)
if PLUGIN_ROOT not in sys.path:
sys.path.insert(0, PLUGIN_ROOT)
if PLUGIN_ROOT and PLUGIN_ROOT not in sys.path:
sys.path.insert(0, PLUGIN_ROOT)
try:
from hookify.core.config_loader import load_rules
from hookify.core.rule_engine import RuleEngine
from core.config_loader import load_rules
from core.rule_engine import RuleEngine
except ImportError as e:
error_msg = {"systemMessage": f"Hookify import error: {e}"}
print(json.dumps(error_msg), file=sys.stdout)

View File

@@ -9,22 +9,14 @@ import os
import sys
import json
# CRITICAL: Add plugin root to Python path for imports
# We need to add the parent of the plugin directory so Python can find "hookify" package
# Add plugin root to Python path for imports
PLUGIN_ROOT = os.environ.get('CLAUDE_PLUGIN_ROOT')
if PLUGIN_ROOT:
# Add the parent directory of the plugin
parent_dir = os.path.dirname(PLUGIN_ROOT)
if parent_dir not in sys.path:
sys.path.insert(0, parent_dir)
# Also add PLUGIN_ROOT itself in case we have other scripts
if PLUGIN_ROOT not in sys.path:
sys.path.insert(0, PLUGIN_ROOT)
if PLUGIN_ROOT and PLUGIN_ROOT not in sys.path:
sys.path.insert(0, PLUGIN_ROOT)
try:
from hookify.core.config_loader import load_rules
from hookify.core.rule_engine import RuleEngine
from core.config_loader import load_rules
from core.rule_engine import RuleEngine
except ImportError as e:
# If imports fail, allow operation and log error
error_msg = {"systemMessage": f"Hookify import error: {e}"}

View File

@@ -9,18 +9,14 @@ import os
import sys
import json
# CRITICAL: Add plugin root to Python path for imports
# Add plugin root to Python path for imports
PLUGIN_ROOT = os.environ.get('CLAUDE_PLUGIN_ROOT')
if PLUGIN_ROOT:
parent_dir = os.path.dirname(PLUGIN_ROOT)
if parent_dir not in sys.path:
sys.path.insert(0, parent_dir)
if PLUGIN_ROOT not in sys.path:
sys.path.insert(0, PLUGIN_ROOT)
if PLUGIN_ROOT and PLUGIN_ROOT not in sys.path:
sys.path.insert(0, PLUGIN_ROOT)
try:
from hookify.core.config_loader import load_rules
from hookify.core.rule_engine import RuleEngine
from core.config_loader import load_rules
from core.rule_engine import RuleEngine
except ImportError as e:
error_msg = {"systemMessage": f"Hookify import error: {e}"}
print(json.dumps(error_msg), file=sys.stdout)

View File

@@ -9,18 +9,14 @@ import os
import sys
import json
# CRITICAL: Add plugin root to Python path for imports
# Add plugin root to Python path for imports
PLUGIN_ROOT = os.environ.get('CLAUDE_PLUGIN_ROOT')
if PLUGIN_ROOT:
parent_dir = os.path.dirname(PLUGIN_ROOT)
if parent_dir not in sys.path:
sys.path.insert(0, parent_dir)
if PLUGIN_ROOT not in sys.path:
sys.path.insert(0, PLUGIN_ROOT)
if PLUGIN_ROOT and PLUGIN_ROOT not in sys.path:
sys.path.insert(0, PLUGIN_ROOT)
try:
from hookify.core.config_loader import load_rules
from hookify.core.rule_engine import RuleEngine
from core.config_loader import load_rules
from core.rule_engine import RuleEngine
except ImportError as e:
error_msg = {"systemMessage": f"Hookify import error: {e}"}
print(json.dumps(error_msg), file=sys.stdout)

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

@@ -1,9 +1,8 @@
{
"name": "learning-output-style",
"version": "1.0.0",
"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

@@ -120,7 +120,7 @@ Use this workflow for structured, high-quality plugin development from concept t
- YAML frontmatter + markdown body structure
- Parsing techniques for bash scripts (sed, awk, grep patterns)
- Temporarily active hooks (flag files and quick-exit)
- Real-world examples from multi-agent-swarm and ralph-wiggum plugins
- Real-world examples from multi-agent-swarm and ralph-loop plugins
- Atomic file updates and validation
- Gitignore and lifecycle management

View File

@@ -449,7 +449,7 @@ Coordinate with auth-agent on shared types.
- Sends notifications to coordinator if enabled
- Allows quick activation/deactivation via `enabled: true/false`
### ralph-wiggum Plugin
### ralph-loop Plugin
**.claude/ralph-loop.local.md:**
```markdown
@@ -512,7 +512,7 @@ fi
For detailed implementation patterns:
- **`references/parsing-techniques.md`** - Complete guide to parsing YAML frontmatter and markdown bodies
- **`references/real-world-examples.md`** - Deep dive into multi-agent-swarm and ralph-wiggum implementations
- **`references/real-world-examples.md`** - Deep dive into multi-agent-swarm and ralph-loop implementations
### Example Files

View File

@@ -126,7 +126,7 @@ sed "s/^pr_number: .*/pr_number: $PR_NUM/" \
mv temp.md ".claude/multi-agent-swarm.local.md"
```
## ralph-wiggum Plugin
## ralph-loop Plugin
### Settings File Structure
@@ -253,7 +253,7 @@ echo "Ralph loop initialized: .claude/ralph-loop.local.md"
## Pattern Comparison
| Feature | multi-agent-swarm | ralph-wiggum |
| Feature | multi-agent-swarm | ralph-loop |
|---------|-------------------|--------------|
| **File** | `.claude/multi-agent-swarm.local.md` | `.claude/ralph-loop.local.md` |
| **Purpose** | Agent coordination state | Loop iteration state |

View File

@@ -310,7 +310,7 @@ Study the skills in this plugin as examples of best practices:
**plugin-settings skill:**
- Specific triggers: "plugin settings", ".local.md files", "YAML frontmatter"
- References show real implementations (multi-agent-swarm, ralph-wiggum)
- References show real implementations (multi-agent-swarm, ralph-loop)
- Working parsing scripts
Each demonstrates progressive disclosure and strong triggering.

View File

@@ -1,9 +1,8 @@
{
"name": "pr-review-toolkit",
"version": "1.0.0",
"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

@@ -0,0 +1,8 @@
{
"name": "ralph-loop",
"description": "Continuous self-referential AI loops for interactive iterative development, implementing the Ralph Wiggum technique. Run Claude in a while-true loop with the same prompt until task completion.",
"author": {
"name": "Anthropic",
"email": "support@anthropic.com"
}
}

View File

@@ -1,12 +1,12 @@
# Ralph Wiggum Plugin
# Ralph Loop Plugin
Implementation of the Ralph Wiggum technique for iterative, self-referential AI development loops in Claude Code.
## What is Ralph?
## What is Ralph Loop?
Ralph is a development methodology based on continuous AI agent loops. As Geoffrey Huntley describes it: **"Ralph is a Bash loop"** - a simple `while true` that repeatedly feeds an AI agent a prompt file, allowing it to iteratively improve its work until completion.
Ralph Loop is a development methodology based on continuous AI agent loops. As Geoffrey Huntley describes it: **"Ralph is a Bash loop"** - a simple `while true` that repeatedly feeds an AI agent a prompt file, allowing it to iteratively improve its work until completion.
The technique is named after Ralph Wiggum from The Simpsons, embodying the philosophy of persistent iteration despite setbacks.
This technique is inspired by the Ralph Wiggum coding technique (named after the character from The Simpsons), embodying the philosophy of persistent iteration despite setbacks.
### Core Concept

View File

@@ -0,0 +1,18 @@
---
description: "Cancel active Ralph Loop"
allowed-tools: ["Bash(test -f .claude/ralph-loop.local.md:*)", "Bash(rm .claude/ralph-loop.local.md)", "Read(.claude/ralph-loop.local.md)"]
hide-from-slash-command-tool: "true"
---
# Cancel Ralph
To cancel the Ralph loop:
1. Check if `.claude/ralph-loop.local.md` exists using Bash: `test -f .claude/ralph-loop.local.md && echo "EXISTS" || echo "NOT_FOUND"`
2. **If NOT_FOUND**: Say "No active Ralph loop found."
3. **If EXISTS**:
- Read `.claude/ralph-loop.local.md` to get the current iteration number from the `iteration:` field
- Remove the file using Bash: `rm .claude/ralph-loop.local.md`
- Report: "Cancelled Ralph loop (was at iteration N)" where N is the iteration value

View File

@@ -1,14 +1,14 @@
---
description: "Explain Ralph Wiggum technique and available commands"
description: "Explain Ralph Loop plugin and available commands"
---
# Ralph Wiggum Plugin Help
# Ralph Loop Plugin Help
Please explain the following to the user:
## What is the Ralph Wiggum Technique?
## What is Ralph Loop?
The Ralph Wiggum technique is an iterative development methodology based on continuous AI loops, pioneered by Geoffrey Huntley.
Ralph Loop implements the Ralph Wiggum technique - an iterative development methodology based on continuous AI loops, pioneered by Geoffrey Huntley.
**Core concept:**
```bash

View File

@@ -0,0 +1,18 @@
---
description: "Start Ralph Loop in current session"
argument-hint: "PROMPT [--max-iterations N] [--completion-promise TEXT]"
allowed-tools: ["Bash(${CLAUDE_PLUGIN_ROOT}/scripts/setup-ralph-loop.sh:*)"]
hide-from-slash-command-tool: "true"
---
# Ralph Loop Command
Execute the setup script to initialize the Ralph loop:
```!
"${CLAUDE_PLUGIN_ROOT}/scripts/setup-ralph-loop.sh" $ARGUMENTS
```
Please work on the task. When you try to exit, the Ralph loop will feed the SAME PROMPT back to you for the next iteration. You'll see your previous work in files and git history, allowing you to iterate and improve.
CRITICAL RULE: If a completion promise is set, you may ONLY output it when the statement is completely and unequivocally TRUE. Do not output false promises to escape the loop, even if you think you're stuck or should exit for other reasons. The loop is designed to continue until genuine completion.

View File

@@ -1,5 +1,5 @@
{
"description": "Ralph Wiggum plugin stop hook for self-referential loops",
"description": "Ralph Loop plugin stop hook for self-referential loops",
"hooks": {
"Stop": [
{

View File

@@ -1,6 +1,6 @@
#!/bin/bash
# Ralph Wiggum Stop Hook
# Ralph Loop Stop Hook
# Prevents session exit when a ralph-loop is active
# Feeds Claude's output back as input to continue the loop

View File

@@ -29,7 +29,7 @@ OPTIONS:
-h, --help Show this help message
DESCRIPTION:
Starts a Ralph Wiggum loop in your CURRENT session. The stop hook prevents
Starts a Ralph Loop in your CURRENT session. The stop hook prevents
exit and feeds your output back as input until completion or iteration limit.
To signal completion, you must output: <promise>YOUR_PHRASE</promise>
@@ -174,3 +174,30 @@ if [[ -n "$PROMPT" ]]; then
echo ""
echo "$PROMPT"
fi
# Display completion promise requirements if set
if [[ "$COMPLETION_PROMISE" != "null" ]]; then
echo ""
echo "═══════════════════════════════════════════════════════════"
echo "CRITICAL - Ralph Loop Completion Promise"
echo "═══════════════════════════════════════════════════════════"
echo ""
echo "To complete this loop, output this EXACT text:"
echo " <promise>$COMPLETION_PROMISE</promise>"
echo ""
echo "STRICT REQUIREMENTS (DO NOT VIOLATE):"
echo " ✓ Use <promise> XML tags EXACTLY as shown above"
echo " ✓ The statement MUST be completely and unequivocally TRUE"
echo " ✓ Do NOT output false statements to exit the loop"
echo " ✓ Do NOT lie even if you think you should exit"
echo ""
echo "IMPORTANT - Do not circumvent the loop:"
echo " Even if you believe you're stuck, the task is impossible,"
echo " or you've been running too long - you MUST NOT output a"
echo " false promise statement. The loop is designed to continue"
echo " until the promise is GENUINELY TRUE. Trust the process."
echo ""
echo " If the loop should stop, the promise statement will become"
echo " true naturally. Do not force it by lying."
echo "═══════════════════════════════════════════════════════════"
fi

View File

@@ -1,9 +0,0 @@
{
"name": "ralph-wiggum",
"version": "1.0.0",
"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"
}
}

View File

@@ -1,26 +0,0 @@
---
description: "Cancel active Ralph Wiggum loop"
allowed-tools: ["Bash"]
hide-from-slash-command-tool: "true"
---
# Cancel Ralph
```!
if [[ -f .claude/ralph-loop.local.md ]]; then
ITERATION=$(grep '^iteration:' .claude/ralph-loop.local.md | sed 's/iteration: *//')
echo "FOUND_LOOP=true"
echo "ITERATION=$ITERATION"
else
echo "FOUND_LOOP=false"
fi
```
Check the output above:
1. **If FOUND_LOOP=false**:
- Say "No active Ralph loop found."
2. **If FOUND_LOOP=true**:
- Use Bash: `rm .claude/ralph-loop.local.md`
- Report: "Cancelled Ralph loop (was at iteration N)" where N is the ITERATION value from above.

View File

@@ -1,48 +0,0 @@
---
description: "Start Ralph Wiggum loop in current session"
argument-hint: "PROMPT [--max-iterations N] [--completion-promise TEXT]"
allowed-tools: ["Bash(${CLAUDE_PLUGIN_ROOT}/scripts/setup-ralph-loop.sh)"]
hide-from-slash-command-tool: "true"
---
# Ralph Loop Command
Execute the setup script to initialize the Ralph loop:
```!
"${CLAUDE_PLUGIN_ROOT}/scripts/setup-ralph-loop.sh" $ARGUMENTS
# Extract and display completion promise if set
if [ -f .claude/ralph-loop.local.md ]; then
PROMISE=$(grep '^completion_promise:' .claude/ralph-loop.local.md | sed 's/completion_promise: *//' | sed 's/^"\(.*\)"$/\1/')
if [ -n "$PROMISE" ] && [ "$PROMISE" != "null" ]; then
echo ""
echo "═══════════════════════════════════════════════════════════"
echo "CRITICAL - Ralph Loop Completion Promise"
echo "═══════════════════════════════════════════════════════════"
echo ""
echo "To complete this loop, output this EXACT text:"
echo " <promise>$PROMISE</promise>"
echo ""
echo "STRICT REQUIREMENTS (DO NOT VIOLATE):"
echo " ✓ Use <promise> XML tags EXACTLY as shown above"
echo " ✓ The statement MUST be completely and unequivocally TRUE"
echo " ✓ Do NOT output false statements to exit the loop"
echo " ✓ Do NOT lie even if you think you should exit"
echo ""
echo "IMPORTANT - Do not circumvent the loop:"
echo " Even if you believe you're stuck, the task is impossible,"
echo " or you've been running too long - you MUST NOT output a"
echo " false promise statement. The loop is designed to continue"
echo " until the promise is GENUINELY TRUE. Trust the process."
echo ""
echo " If the loop should stop, the promise statement will become"
echo " true naturally. Do not force it by lying."
echo "═══════════════════════════════════════════════════════════"
fi
fi
```
Please work on the task. When you try to exit, the Ralph loop will feed the SAME PROMPT back to you for the next iteration. You'll see your previous work in files and git history, allowing you to iterate and improve.
CRITICAL RULE: If a completion promise is set, you may ONLY output it when the statement is completely and unequivocally TRUE. Do not output false promises to escape the loop, even if you think you're stuck or should exit for other reasons. The loop is designed to continue until genuine completion.

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

@@ -1,9 +1,8 @@
{
"name": "security-guidance",
"version": "1.0.0",
"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)