Skip to main content

​
Overview

Plugins extend your AI agents’ capabilities with pre-built integrations, language servers, code quality tools, and more. Unlike skills (which are Markdown instructions you write yourself), plugins are published packages from plugin marketplaces that add entire tool ecosystems to your coding agents.

​
How Plugins Work

Plugins are identified by a name@marketplace format (e.g., github@claude-plugins-official). When you enable a plugin, Whim resolves it from the marketplace and makes its tools available to agents running in your workspace.

​
Available Marketplaces

Whim supports two built-in plugin marketplaces:

Claude Code Plugins

Anthropic’s first-party plugins for Claude Code agents. Includes development workflows, testing tools, and agent capabilities.

Claude Plugins Official

Anthropic’s official plugin registry with integrations, language servers, infrastructure tools, and more.
You can also define custom marketplaces that point to GitHub repositories, enabling private or organization-specific plugins.

​
Plugin Catalog

​
Claude Code Plugins

Agent capabilities and development workflows:
PluginDescription
frontend-designCreate production-grade frontend interfaces
code-reviewReview code changes with detailed feedback
commit-commandsGenerate conventional commit messages
e2e-testingEnd-to-end testing with browser automation
add-testidsAdd test IDs to UI components
code-simplifierReview and simplify code
questionsAsk clarifying questions before proceeding
codexCreate implementation plans with high reasoning
exploreFast codebase exploration
planArchitecture and implementation planning

​
Official Plugins — Language Servers

Language intelligence for your agents:
PluginLanguage
lsp-typescriptTypeScript / JavaScript
lsp-pythonPython
lsp-rustRust
lsp-goGo
lsp-javaJava
lsp-csharpC#
lsp-rubyRuby
lsp-phpPHP
lsp-swiftSwift
lsp-kotlinKotlin
lsp-html-cssHTML & CSS
lsp-yamlYAML
lsp-jsonJSON

​
Official Plugins — Integrations

Connect to the services your team uses:
PluginService
githubGitHub
slackSlack
linearLinear
jiraJira
notionNotion
confluenceConfluence
google-driveGoogle Drive
google-sheetsGoogle Sheets
google-calendarGoogle Calendar
stripeStripe
supabaseSupabase
sentrySentry
datadogDatadog
pagerdutyPagerDuty

​
Official Plugins — Infrastructure & DevOps

PluginDescription
dockerDocker container management
kubernetesKubernetes cluster operations
terraformInfrastructure as code
awsAmazon Web Services
azureMicrosoft Azure
gcpGoogle Cloud Platform
vercelVercel deployments
netlifyNetlify deployments
cloudflareCloudflare services

​
Official Plugins — Code Quality & Testing

PluginDescription
eslintJavaScript/TypeScript linting
prettierCode formatting
stylelintCSS linting
jestJest test runner
vitestVitest test runner
pytestPython test runner
snykSecurity vulnerability scanning
sonarqubeCode quality analysis
dependabotDependency updates

​
Official Plugins — Data

PluginDescription
postgresPostgreSQL database
redisRedis cache and data store
mongodbMongoDB database

​
Enabling Plugins

1

Open plugin settings

Go to Settings > Plugins in your workspace or user preferences.
2

Browse the catalog

Search by name or filter by category to find plugins. Each plugin shows which marketplace it comes from.
3

Toggle plugins on or off

Click the toggle to enable or disable a plugin. Changes take effect for new tasks.

​
Plugin Scope

Like skills, plugins can be configured at two levels:

​
Workspace Plugins

  • Configured by workspace admins in Settings > Workspace Defaults > Plugins
  • Available to all workspace members by default
  • Individual members can disable workspace plugins in their own configuration

​
User Plugins

  • Configured in Settings > User Defaults > Plugins
  • Available across all of your workspaces
  • Can override or supplement workspace plugins

​
Resolution Order

  1. Workspace plugins — all enabled plugins from workspace defaults
  2. Minus disabled — remove any workspace plugins the user has disabled
  3. Plus user plugins — merge in the user’s personal plugins

​
Custom Marketplaces

If your organization publishes its own plugins, you can add custom marketplace definitions:
  1. Go to Settings > Plugins.
  2. Under advanced configuration, add a marketplace by specifying its name and GitHub repository source.
{
  "my-org-plugins": {
    "source": {
      "source": "github",
      "repo": "my-org/claude-plugins"
    }
  }
}
Plugins from custom marketplaces are referenced as plugin-name@my-org-plugins.
The two built-in marketplaces (claude-code-plugins and claude-plugins-official) are automatically configured. You only need to add custom marketplace definitions for private or third-party registries.

​
Importing from Settings

You can import plugin configurations from a Claude Code settings.json file:
  1. Go to Settings > Plugins.
  2. Use the import option and paste your settings.json content.
  3. Whim validates the plugin identifiers and auto-populates known marketplace definitions.

​
Limits

ConstraintLimit
Plugins per workspace/user config100
Custom marketplaces50
Marketplace name1–100 characters, alphanumeric, hyphens, and underscores