---
title:

Useful Plugins for Claude Code

date: 2026-03-20
draft: false
---

Claude Code has so-called plugins. And recently messengers were added there, as a response to OpenClaw.

A plugin is, roughly speaking, a folder with a set of resources:

  • commands/ — slash commands
  • skills/ — agent skills (triggered automatically by context)
  • agents/ — subagents for specialized tasks
  • hooks/ — event handlers (PreToolUse, PostToolUse, SessionStart and so on)
  • .mcp.json — MCP server configuration
  • .lsp.json — LSP server configuration
  • settings.json — default settings
  • .claude-plugin/plugin.json — plugin description

Messenger plugins (discord, telegram, slack) work through the channels mechanism — MCP servers that push external events into a running session. The session is launched with the --channels flag, messages from unknown senders are dropped (allowlist + pairing code). Still in research preview.

The catalog has grown noticeably — at the time of writing there are 30 official and 16 external plugins. Most are focused tools that cover a specific need. Here’s what I found useful:

  • security-guidance: a PreToolUse hook in Python. Before each Edit/Write/MultiEdit it analyzes changes for vulnerabilities: command injection, XSS, unsafe patterns.
  • playground: creates interactive HTML playgrounds — self-contained single-file visual explorers with controls and live preview. Templates: design-playground, data-explorer, concept-map, document-critique. Turned out to be useful for explaining complex constructs.
  • frontend-design: so that designs aren’t blatantly identical. Picks a random style + anti-patterns for typical traits.
  • pr-review-toolkit: 6 specialized agents for PR review: comment-analyzer, pr-test-analyzer, silent-failure-hunter, type-design-analyzer, code-reviewer, code-simplifier.
  • feature-dev: a structured 7-phase workflow for feature development. The /feature-dev command. Phases: discovery, codebase exploration (parallel agents), clarifying questions, architecture design (2-3 approaches with trade-offs), implementation, quality review (3 parallel reviewer agents), summary.
  • …plus separate plugins for LSP that provide smart navigation like in full-featured IDEs: go-to-definition, find-references, hover, document-symbols, diagnostics.

From the external plugins:

  • context7: pulls up-to-date documentation and code examples directly from library repositories into context. Versioned, from primary sources.
  • discord, telegram, slack: messenger bridges for Claude Code.
  • greptile: AI PR review on GitHub/GitLab, viewing and resolving comments directly from Claude Code.
  • serena: semantic code analysis — intelligent navigation, refactoring hints via LSP integration.