Community & Ecosystem
The Claude Code extension ecosystem is growing fast. These are the projects, tools, and people building it. I've used many of these myself — here's what's actually worth your time.
Every project listed here is open source and maintained by individual developers or small teams. If a tool saves you time, consider starring the repo, sponsoring the developer, or contributing a PR. That's how ecosystems stay healthy.
Memory Systems
Claude Code's built-in memory (CLAUDE.md, auto-memory) is file-based and keyword-matched. These community projects add semantic, persistent, cross-session memory.
A markdown-based semantic memory system that maintains persistent context across sessions through Claude Code's hook system. Unlike suggestion-based memory, it enforces memory persistence at three lifecycle points.
How it works:
- SessionStart hook — Loads full context and scratchpad when sessions begin
- UserPromptSubmit hook — Injects state reminders with every prompt (survives context compaction)
- SessionEnd hook — Archives scratchpad and prompts context updates
File structure: Dynamic memory lives in .claude/memory/ (context.md, scratchpad.md, decisions.md, session archives). Static docs live in .ai/ (architecture, patterns, workflows).
Claimed reliability: CLAUDE.md alone ~30%, + SessionStart ~50%, + UserPromptSubmit ~75%, + Orchestrator mode ~95%.
Automatically captures everything Claude does during coding sessions, compresses it with AI (Claude Agent SDK), and injects relevant context back into future sessions.
Key features:
- Progressive disclosure — layered memory retrieval with token cost visibility
- Skill-based search (
mem-searchskill for querying memories) - Web viewer UI at localhost:37777
- Privacy control —
<private>tags exclude sensitive content
Photographic memory in ONE portable file. No database, no SQLite, no ChromaDB — just a single .mv2 file you can git commit, scp, or share. Native Rust core with sub-millisecond operations.
Memory System Comparison
| System | Approach | Storage | Stars |
|---|---|---|---|
| Built-in (CLAUDE.md) | File-based, keyword match | Markdown files | N/A |
| Severance | Hook-enforced, 3 lifecycle points | Markdown + archives | Growing |
| Claude-Mem | AI-compressed, progressive disclosure | Local + web viewer | 12.9K+ |
| Claude-Brain | Vector embeddings, Rust core | Single .mv2 file | Growing |
| Memsearch | Semantic search, auto-inject top-3 | CLI-based | Growing |
Curated Lists & Directories
The most comprehensive curated list of Claude Code extensions. 150+ projects organized by category: code intelligence, dev workflows, integrations, themes, agent orchestrators, and more.
135 agents, 35 curated skills (+400K via SkillKit), 42 commands, 150+ plugins, 19 hooks, 15 rules, 7 templates, 8 MCP configs. Organized with quick-navigation tables.
Automated collection of plugin adoption metrics across GitHub repos using n8n workflows. See which plugins are actually being used, not just starred.
Notable Community Tools
CCUsage — Usage Monitor
Track your Claude Code spending in real-time. See token usage, cost per session, and spending trends. Essential if you're on the Max plan and want to stay within budget.
TDD Skills Collection
Skills that enforce test-driven development workflows: write tests first, implement to pass, refactor. Includes /tdd command that scaffolds test files and guides implementation.
Britfix — Spelling Hook
A hook that converts American spellings to British English after file edits. A fun, niche example of how creative hooks can be.
cc-tools — High-Performance Hooks
Go implementation of hooks and utilities. When shell scripts are too slow, these compiled binaries handle high-frequency hook events with minimal latency.
Where to Find More
-
GitHub Topics — Search for
claude-code-plugin,claude-code-skill, ormcp-servertopics - claudemarketplaces.com — 2,300+ skills, 770+ MCP servers, 95+ marketplaces aggregated
- Official Docs — code.claude.com/docs for the authoritative reference
- Anthropic Discord — Active extension-building channels with direct access to the community
- modelcontextprotocol.io — The MCP spec and directory of servers across all clients
Contributing to the Ecosystem
This is still early days. The best extensions haven't been built yet. Here's how to get involved:
-
Share what works
Found a great hook config? Built a useful skill? Post it on GitHub with the
claude-codetopic. Even a single well-documented hook helps someone. -
Build MCP servers for internal tools
Got an internal API or custom tool? Wrap it as an MCP server. The protocol is simple and the SDK handles the hard parts. Then consider open-sourcing it.
-
Contribute to awesome-claude-code
Submit PRs to the curated lists. Help others discover the best tools. Good curation is as valuable as good code.
-
Sponsor developers who save you time
If a plugin or skill saves you hours, a $5/month GitHub Sponsors subscription is the best way to keep it maintained.
Many of the best Claude Code extensions haven't been built yet. If you have a workflow that could help others, now is the time to package and share it. The community rewards early contributors.