Claude Code 资源精选列表

Awesome Claude Code

A curated list of awesome tools, skills, MCP servers, tips, and resources for Claude Code -- Anthropic's agentic coding tool that lives in your terminal.

Claude Code understands your codebase, executes routine tasks, explains complex code, and handles git workflows through natural language. This list collects the best ecosystem resources to help you get the most out of it.

Contents

• Official Resources
• Skills and Plugins
• MCP Servers
  • Code and Development
  • Browser and Web
  • Data and Database
  • Productivity and Communication
  • Cloud and Infrastructure
  • Security and Reverse Engineering
  • MCP Frameworks and Tooling
• Slash Commands
• CLI Extensions and Companion Tools
• GUI and Remote Clients
• Monitoring and Cost Tracking
• Workflow and Multi-Agent Tools
• Configuration and Tips
  • CLAUDE.md Best Practices
  • Settings and Permissions
  • Model Selection and Cost Optimization
  • Keyboard Shortcuts
• Working Effectively with Claude Code
  • The Paradigm Shift
  • Verification-First Development
  • Documentation-First: Compound Interest Programming
  • Master Mindset: Delegate, Don't Dictate
  • Autonomous Execution: Minimize Human-in-the-Loop
  • Context Hygiene
  • Multi-Agent Orchestration Patterns
• Tutorials and Guides
• Alternative Coding Agents
• Community

Official Resources

• Claude Code - The official Claude Code repository from Anthropic.
• Claude Code Documentation - Official documentation covering installation, usage, and configuration.
• Model Context Protocol Specification - The formal MCP spec that powers Claude Code's extensibility.
• MCP Server Registry - Community-driven registry of Model Context Protocol servers.
• MCP Inspector - Visual testing tool for MCP servers.
• Anthropic Claude Code Plugins (Official) - Official Anthropic-managed directory of high quality Claude Code plugins.
• Anthropic Cookbook - Official recipes and patterns for building with Claude, including Claude Code examples.
• Claude Code Blog Post - Anthropic's announcement and overview of Claude Code.

Skills and Plugins

Skills are reusable markdown-based instructions that extend Claude Code's capabilities with domain-specific expertise.

• everything-claude-code - Complete Claude Code configuration collection: agents, skills, hooks, commands, rules, and MCPs. Battle-tested from an Anthropic hackathon winner.
• Awesome Claude Skills (Composio) - Curated list of Claude Skills, resources, and tools for customizing Claude AI workflows.
• UI/UX Pro Max Skill - AI skill providing design intelligence for building professional UI/UX across multiple platforms.
• Antigravity Awesome Skills - The ultimate collection of 800+ agentic skills for Claude Code, Antigravity, and Cursor.
• Planning with Files - Claude Code skill implementing Manus-style persistent markdown planning.
• Awesome Claude Code Subagents - Collection of 100+ specialized Claude Code subagents covering a wide range of development use cases.
• Awesome Agent Skills (VoltAgent) - 300+ agent skills from official dev teams and the community, compatible with Claude Code, Codex, Gemini CLI, and more.
• Awesome Claude Skills (travisvn) - Curated list of Claude Skills and resources for customizing Claude AI workflows.
• Awesome Agent Skills (heilcheng) - Curated skills, tools, tutorials, and capabilities for AI coding agents.
• Claude Code Infrastructure Showcase - Examples of Claude Code infrastructure with skill auto-activation, hooks, and agents.
• Marketing Skills - Marketing skills for Claude Code: CRO, copywriting, SEO, analytics, and growth engineering.
• Awesome Claude Code Plugins - Curated list of plugins that extend Claude Code with custom commands, agents, hooks, and MCP servers.
• Awesome LLM Skills - Curated list of LLM and AI Agent Skills that work with Claude Code, Codex, Gemini CLI, and custom agents.
• Claude Code Skill Factory - Toolkit for building and deploying production-ready Claude Skills, agents, and slash commands at scale.
• Claude Code Tresor - Collection of autonomous skills, expert agents, slash commands, and prompts for Claude Code.
• BMAD Method Skills - BMAD Method skills for Claude Code with auto-detection, memory integration, and slash commands.
• SuperClaude Framework - Configuration framework enhancing Claude Code with specialized commands, cognitive personas, and development methodologies.

MCP Servers

The Model Context Protocol (MCP) allows Claude Code to interact with external tools and data sources. Below are popular MCP servers organized by category.

Code and Development

• GitHub MCP Server - GitHub's official MCP server for repository management, issues, PRs, and more.
• Context7 - Up-to-date code documentation for LLMs and AI code editors.
• Serena - Powerful coding agent toolkit providing semantic retrieval and editing capabilities.
• GitMCP - Free, open-source remote MCP server for any GitHub project to eliminate code hallucinations.
• DesktopCommanderMCP - MCP server providing terminal control, file system search, and diff file editing capabilities.
• Pal MCP Server - Bridges Claude Code with Gemini, OpenAI, OpenRouter, Azure, Grok, Ollama, and more as one unified tool.

Browser and Web

• Playwright MCP - Microsoft's Playwright MCP server for browser automation.
• Figma Context MCP - Provides Figma layout information to AI coding agents.
• MCP Chrome - Chrome extension-based MCP server for browser automation, content analysis, and semantic search.
• Browser MCP - Model Context Provider server that allows AI applications to control your browser.
• Firecrawl MCP Server - Official Firecrawl MCP server adding powerful web scraping and search to Claude and other LLM clients.
• MCP Playwright - Playwright MCP server to automate browsers and APIs in Claude Desktop, Cline, and Cursor.
• WhatsApp MCP - WhatsApp MCP server for messaging integration.

Data and Database

• MindsDB - Federated query engine for AI, acting as a comprehensive MCP server.
• GenAI Toolbox for Databases - Google's MCP toolbox for databases.
• Kreuzberg - Polyglot document intelligence framework for text extraction from PDFs, Office docs, images, and 75+ formats. Available as CLI, REST API, or MCP server.

Productivity and Communication

• Activepieces - AI workflow automation platform with 400+ MCP servers for agents.
• Apple MCP - Collection of Apple-native tools for the Model Context Protocol.

Cloud and Infrastructure

• AWS MCP Servers - Official MCP servers for AWS services.

Security and Reverse Engineering

• HexStrike AI - Advanced MCP server for 150+ cybersecurity tools covering automated pentesting, vulnerability discovery, and security research.
• GhidraMCP - AI-powered reverse engineering assistant bridging IDA Pro with language models through MCP.
• IDA Pro MCP - MCP server for IDA Pro reverse engineering.

MCP Frameworks and Tooling

• FastMCP - The fast, Pythonic way to build MCP servers and clients.
• MCP Use - Fullstack MCP framework to develop MCP apps for ChatGPT, Claude, and AI agents.
• FastAPI MCP - Expose your FastAPI endpoints as MCP tools with authentication.
• Awesome MCP Servers - The definitive collection of MCP servers.
• Awesome MCP Servers (appcypher) - Another curated list of Model Context Protocol servers.
• MCP for Beginners - Microsoft's open-source curriculum introducing MCP fundamentals with real-world examples in multiple languages.
• Metorial - Connect any AI model to 600+ integrations powered by MCP.
• ACI.dev - Open source tool-calling platform with 600+ tools through direct function calling or a unified MCP server.

Slash Commands

Custom slash commands extend Claude Code's built-in command palette with project-specific or general-purpose workflows.

• Claude Code Commands - Collection of production-ready slash commands for Claude Code.
• Claude Sessions - Custom slash commands providing comprehensive development session tracking and documentation.
• Claude Command Suite - Professional slash commands for structured workflows: code review, feature creation, security auditing, and architectural analysis.
• Awesome Claude Code Plugins (ccplugins) - Curated list of slash commands, subagents, MCP servers, and hooks for Claude Code.
• Awesome Claude Code Setup - Power user collection of bash scripts and slash commands for Claude Code.
• ccexp - Interactive terminal interface for discovering, previewing, and managing Claude Code configuration files and slash commands.

CLI Extensions and Companion Tools

Tools that extend or complement the Claude Code CLI experience.

• CC Switch - Cross-platform desktop all-in-one assistant tool for Claude Code, Codex, OpenCode, and Gemini CLI.
• Claude Mem - Plugin that automatically captures everything Claude does, compresses it with AI, and injects relevant context into future sessions.
• Claude Code Router - Use Claude Code as the foundation for coding infrastructure while controlling model interaction.
• Claude Code Templates - CLI tool for configuring and monitoring Claude Code.
• AionUI - Free, local, open-source 24/7 cowork app for Gemini CLI, Claude Code, Codex, OpenCode, and more.
• Claude Squad - Manage multiple AI terminal agents like Claude Code, Aider, Codex, OpenCode, and Amp simultaneously.
• Vibe Kanban - Get 10x more out of Claude Code, Codex, or any coding agent with kanban-style task management.
• Agents (wshobson) - Intelligent automation and multi-agent orchestration for Claude Code.

GUI and Remote Clients

Graphical and remote interfaces for interacting with Claude Code beyond the terminal.

• OpCode - Powerful GUI app and toolkit for Claude Code: custom agents, interactive sessions, and secure background agents.
• Happy - Mobile and web client for Codex and Claude Code with real-time voice, encryption, and full features.
• CloudCLI (Claude Code UI) - Free open-source web UI and GUI for managing Claude Code sessions and projects remotely.
• Claudable - Open-source web builder leveraging local CLI agents like Claude Code, Codex, and Gemini CLI.
• CodePilot - Native desktop GUI for Claude Code built with Electron and Next.js.
• Companion - Web and mobile UI for Claude Code and Codex with session launching, response streaming, and tool approval.
• IDEA Claude Code GUI - IntelliJ IDEA plugin providing a GUI for Claude Code.
• Claude Code Remote (Telegram/Email/Discord) - Control Claude Code remotely via email, Discord, or Telegram with task notifications and reply-to-command.
• Claude Code Telegram - Telegram bot providing remote access to Claude Code with full AI assistance and session persistence.
• Claude Code Telegram (hanxiao) - Telegram bridge for Claude Code.

Monitoring and Cost Tracking

Tools for tracking token usage, API costs, and session analytics.

• Claude Code Statusline - Transform your terminal with atomic precision statusline featuring real-time cost tracking, MCP monitoring, and beautiful themes.
• Claude Dashboard - Comprehensive status line plugin with context usage, API rate limits, and cost tracking.
• Splitrail - Fast, cross-platform, real-time token usage tracker and cost monitor for Gemini CLI, Claude Code, Codex CLI, and more.
• Claude Usage Tracker - Track Claude Code API usage from your macOS menu bar with accurate cost calculations.
• toktrack - Ultra-fast token and cost tracker for LLM token usage including Claude Code.
• cccost - Instrument Claude Code to track actual token usage and cost.
• claude-loop - Automation toolkit for running iterative Claude Code sessions with cost tracking and monitoring.

Workflow and Multi-Agent Tools

Orchestration frameworks, CI/CD integrations, and multi-agent patterns for Claude Code.

• Agents (wshobson) - Intelligent automation and multi-agent orchestration for Claude Code.
• Awesome Claude Agents - An orchestrated sub-agent dev team powered by Claude Code.
• Claude Squad - Manage multiple AI terminal agents like Claude Code, Aider, Codex, and OpenCode.
• Vibe Kanban - Kanban-style task management to coordinate work across Claude Code, Codex, or any coding agent.
• Remote Agentic Coding System - Connect Claude Code or Codex to Slack, Telegram, GitHub, and more.
• Daytona - Secure and elastic infrastructure for running AI-generated code.
• Awesome Claude Code (hesreallyhim) - Curated list of skills, hooks, slash-commands, agent orchestrators, applications, and plugins.

Multi-Agent Patterns

Claude Code supports spawning subagents with Task and Agent tools. Common orchestration patterns include:

• Coordinator-Worker - A coordinator agent delegates tasks to specialized worker agents, each with their own CLAUDE.md instructions and tool permissions.
• Judge-Review - After workers complete tasks, a judge agent reviews output quality before the coordinator accepts or requests revisions.
• Pipeline - Agents are chained sequentially, where each agent's output becomes the next agent's input (e.g., plan -> implement -> test -> review).
• God Mode - Autonomous long-running orchestration where a coordinator manages workers and judges, reporting results via email or messaging while the user is away.

Configuration and Tips

CLAUDE.md Best Practices

CLAUDE.md is the primary way to give Claude Code persistent project context. It is automatically loaded when Claude Code starts in a directory.

• Place CLAUDE.md at the project root. It is loaded automatically and applies to all sessions in that directory.
• Use ~/.claude/CLAUDE.md for global instructions that apply across all projects (e.g., preferred coding style, commit message format).
• Keep it concise and actionable. Claude Code reads the full file at session start -- avoid verbose prose and focus on rules and patterns.
• Structure with headers. Use markdown headers to separate concerns: coding standards, testing requirements, project architecture, deployment notes.
• Include file path conventions. Tell Claude Code where to find tests, configs, source code, and documentation.
• Specify tool restrictions. For example: "Never use rm -rf without confirmation" or "Always run tests before committing."
• Reference other instruction files. Use @AGENTS.md or @docs/architecture.md to modularize complex instructions.
• Document naming conventions. Include variable naming, file naming, branch naming, and commit message patterns.
• List forbidden patterns. Explicitly state what Claude Code should NOT do: "Do not modify files in /config/production/".
• Update regularly. As the project evolves, keep CLAUDE.md in sync with reality.

Example minimal CLAUDE.md:

# Project: my-app

## Stack
- TypeScript, React 19, Next.js 15, Tailwind CSS 4
- Testing: Vitest + React Testing Library

## Rules
- All new code must have tests
- Use conventional commits (feat:, fix:, docs:, etc.)
- Never modify .env files directly
- Run `pnpm test` before committing

## Structure
- src/components/ -- React components
- src/lib/ -- Utility functions
- src/app/ -- Next.js app router pages
- tests/ -- Test files mirror src/ structure

Settings and Permissions

Claude Code's behavior can be configured through .claude/settings.json at both project and user levels.

• Project settings (.claude/settings.json in repo root) - Shared with your team via version control.
• User settings (~/.claude/settings.json) - Personal preferences that apply globally.

Key settings to know:

{
  // Allow specific tools to run without asking for permission
  "permissions": {
    "allow": [
      "Bash(npm test)",
      "Bash(npm run lint)",
      "Bash(git status)",
      "Bash(git diff)"
    ],
    "deny": [
      "Bash(rm -rf *)",
      "Bash(git push --force)"
    ]
  }
}

Tips:

• Pre-approve safe commands like git status, git diff, npm test, and npm run lint so Claude Code does not pause for confirmation.
• Deny destructive commands explicitly to prevent accidents with rm -rf, git push --force, DROP TABLE, etc.
• Use glob patterns in permissions for flexibility: Bash(npm run *) allows all npm scripts.
• Scope MCP server permissions per project to avoid exposing sensitive tools across unrelated codebases.

Model Selection and Cost Optimization

• Use /model to switch models during a session. Use the most capable model for complex architectural decisions and switch to faster models for routine tasks.
• Use /compact to compress context when a session gets long. This reduces token usage and costs while preserving important context.
• Use --resume to continue sessions instead of starting fresh, saving the overhead of re-reading the codebase.
• Write focused prompts. Specific, well-scoped requests consume fewer tokens than vague instructions that require multiple rounds of clarification.
• Leverage CLAUDE.md to front-load context so you spend fewer tokens explaining project structure in every conversation.
• Use subagents for parallel work. The Task tool allows Claude Code to spawn focused subagents, each with a narrow scope, reducing token waste from context switching.
• Set --max-turns when running in headless mode to cap autonomous execution and prevent runaway costs.

Keyboard Shortcuts

Key shortcuts available in the Claude Code terminal interface:

Working Effectively with Claude Code

Claude Code is not a chatbot you prompt — it is an autonomous agent you delegate to. The highest-leverage work is not writing better prompts, but engineering a better environment: tests, documentation, permissions, and context management that let Claude self-correct and operate independently.

"Instead of writing code yourself and asking Claude to review it, you describe what you want and Claude figures out how to build it." — Anthropic Official Best Practices

The Paradigm Shift

Verification-First Development

"Include tests, screenshots, or expected outputs so Claude can check itself. This is the single highest-leverage thing you can do." — Anthropic

The key insight: give Claude a way to verify its own work so you stop being the only feedback loop. Without verification criteria, every mistake requires your attention. With tests, Claude self-corrects autonomously.

The TDD pattern with Claude Code:

Write failing tests for a validateEmail function:
- user@example.com → true
- "invalid" → false
- user@.com → false
Then implement the function and make all tests pass.

The verification hierarchy (from most to least autonomous):

1. Test suites — Claude runs tests, sees failures, fixes them without asking you
2. Type checkers / linters — immediate, deterministic feedback
3. Bash commands — curl the endpoint, grep for regressions, diff output
4. Screenshots — for UI work, Claude can visually verify
5. Human review — last resort, not default

Anti-pattern: Telling Claude what to implement without any way to verify. Claude will produce plausible-looking code that may miss edge cases, and you become the test suite.

Documentation-First: Compound Interest Programming

CLAUDE.md is not a prompt — it is persistent institutional knowledge that compounds over time. Every rule you add prevents entire classes of mistakes in all future sessions.

The compounding hierarchy:

What to put in CLAUDE.md:

• Commands Claude cannot guess (pnpm test:e2e --filter=api)
• Style rules that differ from defaults ("use tabs, not spaces")
• Architectural decisions ("all API handlers go through the middleware chain in src/middleware/")
• Common gotchas ("the staging DB requires VPN; use make tunnel first")

What NOT to put in CLAUDE.md:

• Anything Claude can figure out by reading the code
• Standard language conventions
• Verbose explanations (if CLAUDE.md is too long, rules get ignored)

Key insight: Treat CLAUDE.md like code — review it when things go wrong, prune it regularly. If Claude keeps ignoring a rule, the file is too long and the rule is getting lost.

Tell Claude to remember things:

Remember that we use pnpm, not npm, in this project.
Save to memory that API tests require a local Redis instance.

Master Mindset: Delegate, Don't Dictate

"Think of delegating to a capable colleague. Give context and direction, then trust Claude to figure out the details." — Anthropic

Delegation pattern:

The checkout flow is broken for users with expired cards.
The relevant code is in src/payments/. Investigate and fix it.

NOT:

Open src/payments/checkout.js, go to line 142, change x > 0 to x >= 0,
then save, then run npm test, then...

You do not need to specify which files to read or what commands to run. Claude figures that out. It's a conversation — start with what you want, iterate naturally:

> Fix the login bug
[Claude investigates, tries something]
> That's not quite right — the issue is in session handling, not the auth check.
[Claude adjusts approach]

The interview pattern for large features:

I want to add real-time notifications. Interview me about the requirements —
ask about technical constraints, edge cases, and tradeoffs I might not have
considered. When we've covered everything, write a spec to SPEC.md.

Then start a fresh session to implement the spec (clean context).

The four-phase workflow:

1. Explore (Plan Mode) — read files, understand the codebase, no changes
2. Plan (Plan Mode) — create implementation plan, press Ctrl+G to edit in your editor
3. Implement (Normal Mode) — execute the plan, write tests, verify
4. Commit (Normal Mode) — commit, create PR

Autonomous Execution: Minimize Human-in-the-Loop

The goal is to maximize Claude's autonomous operation time. Every permission prompt, every "does this look right?", every manual review is friction that breaks flow.

Permission management (from most to least autonomous):

Headless execution for batch/CI workflows:

# One-off analysis
claude -p "List all API endpoints" --output-format json

# With cost cap
claude -p "Refactor auth module" --max-budget-usd 5.00 --max-turns 20

# Fan-out pattern
for file in $(cat files.txt); do
  claude -p "Migrate $file from React to Vue" \
    --allowedTools "Edit,Bash(git commit *)" \
    --no-session-persistence
done

Notification hooks — get alerted only when Claude actually needs you:

{
  "hooks": {
    "Notification": [{
      "matcher": { "event": "permission_prompt" },
      "hooks": [{ "command": "notify-send 'Claude needs approval'" }]
    }]
  }
}

Context Hygiene

"Most best practices are based on one constraint: Claude's context window fills up fast, and performance degrades as it fills." — Anthropic

The rules:

1. /clear between unrelated tasks — the single most important habit
2. Use subagents for exploration — keeps main context clean for implementation
3. /compact with focus — /compact Focus on the API changes we discussed
4. Split spec and implementation — write spec in one session, implement in a fresh one
5. Esc+Esc to rewind — select checkpoint, "Summarize from here" to compress

The correction spiral anti-pattern: If you have corrected Claude more than twice on the same issue, the context is cluttered with failed approaches. Run /clear and start fresh with a better initial prompt. A clean session with a good prompt almost always outperforms a long session with accumulated corrections.

Context budget awareness:

• Use /context to see what is consuming space
• Delegate high-volume operations (test suites, log analysis) to subagents
• CLAUDE.md is loaded every session — keep it concise or rules get lost

Multi-Agent Orchestration Patterns

Claude Code supports multiple levels of parallelism for complex work:

Level 1: Subagents (within a single session)

Research the auth, database, and API modules in parallel using separate subagents.
Use a subagent to run the full test suite and report only failures.

Subagents run in isolated context windows. They cannot spawn further subagents. Use them to keep exploration noise out of your main context.

Level 2: Writer/Reviewer (two manual sessions)

• Session A writes the implementation
• Session B reviews with fresh context (no implementation bias)

Level 3: Coordinator/Worker/Judge (autonomous orchestration)

• A coordinator decomposes work into tasks
• Workers implement on separate git branches
• Judges review (read-only tools, cannot modify code)
• Failed reviews feed back to workers with specific fixes
• Escalation after N failures

This pattern enables overnight/multi-day autonomous execution where the human only reviews final results.

Level 4: Agent Teams (experimental, CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1)

• One lead session coordinates multiple teammate sessions
• Shared task list with dependencies and inter-agent messaging
• Each teammate has its own independent context window
• Best for: parallel module development, competing debug hypotheses, cross-layer coordination

Summary: The Highest-Leverage Actions

In order of impact:

1. Give Claude verification (tests, linters, type checkers) — the single most impactful thing
2. Manage context aggressively — /clear between tasks, subagents for exploration
3. Invest in CLAUDE.md — compound returns across all future sessions
4. Delegate, don't dictate — describe intent and constraints, not steps
5. Use Plan Mode for complex work — separate thinking from doing
6. Set up permissions and hooks — reduce interruption, guarantee actions
7. Leverage multi-agent patterns — subagents for isolation, teams for parallelism

Tutorials and Guides

Getting Started

• Claude Code Guide (zebbern) - Setup, commands, workflows, agents, skills, and tips.
• Claude Code Guide (Cranot) - Comprehensive Claude Code CLI guide, auto-updated every 2 days.
• MCP for Beginners (Microsoft) - Open-source curriculum introducing MCP fundamentals through real-world examples.
• MCP Chinese Getting Started Guide - MCP getting started guide in Chinese.
• Awesome MCP ZH - MCP resources in Chinese.
• Claude Code Documentation - Official Anthropic documentation.

Advanced Workflows

• everything-claude-code - Battle-tested configurations from an Anthropic hackathon winner covering agents, skills, hooks, commands, and MCPs.
• Claude Code Infrastructure Showcase - Real-world examples of skill auto-activation, hooks, and agent orchestration.
• SuperClaude Framework - Advanced framework with specialized commands, cognitive personas, and development methodologies.

System Prompts and Internals

• System Prompts of AI Tools - Collection of system prompts for Claude Code, Cursor, Windsurf, Devin, and dozens of other AI tools.
• AI System Prompts - Curated collection of system prompts for top AI tools including Claude Code.

Video Tutorials

• Claude Code Official YouTube - Search for official and community video tutorials.
• Building with Claude Code - Community tutorials on building real projects with Claude Code.

Alternative Coding Agents

Other AI-powered coding tools in the same space. Understanding the landscape helps you choose the right tool for each job.

• Claude Code - Anthropic's agentic coding tool in the terminal.
• OpenAI Codex - OpenAI's lightweight coding agent for the terminal.
• Aider - AI pair programming in your terminal, supporting multiple LLM providers.
• Cursor - The AI code editor with deep codebase understanding.
• Roo Code - A whole dev team of AI agents in your code editor.
• OpenCode - Powerful AI coding agent built for the terminal.
• GitHub Copilot CLI - GitHub Copilot coding agent directly in your terminal.
• Cherry Studio - AI productivity studio with smart chat, autonomous agents, and 300+ assistants.
• iFlow CLI - Command-line intelligence that embeds in your terminal for repository analysis and workflow automation.
• TabbyML - Self-hosted AI coding assistant.

Community

• Anthropic Discord - Official Anthropic Discord server with Claude Code channels.
• Claude Code GitHub Discussions - Official discussion forum for Claude Code.
• Claude Code GitHub Issues - Bug reports and feature requests.
• r/ClaudeAI - Reddit community for Claude users, with frequent Claude Code discussions.
• r/ClaudeCode - Dedicated Reddit community for Claude Code.
• Anthropic Blog - Official announcements and technical deep dives.
• MCP Discord - Community Discord for Model Context Protocol development.

Contributing

Contributions welcome! Read the contribution guidelines first.

License

To the extent possible under law, the contributors have waived all copyright and related or neighboring rights to this work. See LICENSE for details.