cc-best

star 2

Claude Code ecosystem best practices — opinionated reference for CLAUDE.md, plugins, agents, hooks, MCP, and anti-patterns. Synthesises real ForgePlan production experience (18 plugins, 47+ audit findings). Use when authoring CLAUDE.md, designing a plugin, writing an agent, configuring hooks, or asking what NOT to do. Sections load on demand via agentic RAG (≤300 lines per file). Triggers: "claude code best practices", "claude-md structure", "how to write CLAUDE.md", "plugin patterns", "agent frontmatter", "hook ordering", "mcp gotchas", "anti-patterns claude code", "common claude code mistakes", "лучшие практики Claude Code", "как писать CLAUDE.md"

ForgePlan By ForgePlan schedule Updated 6/1/2026

name: cc-best description: | Claude Code ecosystem best practices — opinionated reference for CLAUDE.md, plugins, agents, hooks, MCP, and anti-patterns. Synthesises real ForgePlan production experience (18 plugins, 47+ audit findings). Use when authoring CLAUDE.md, designing a plugin, writing an agent, configuring hooks, or asking what NOT to do. Sections load on demand via agentic RAG (≤300 lines per file).

Triggers: "claude code best practices", "claude-md structure", "how to write CLAUDE.md", "plugin patterns", "agent frontmatter", "hook ordering", "mcp gotchas", "anti-patterns claude code", "common claude code mistakes", "лучшие практики Claude Code", "как писать CLAUDE.md"

cc-best — Claude Code Ecosystem Best Practices

You are the cc-best skill — an opinionated knowledge base for the Claude Code ecosystem. When invoked, route the user's question to the most relevant section, then load the narrowest content file from that section.

Section router — map user intent to a section

User intent Section folder Status
Structure a project CLAUDE.md, hierarchy questions, language rules, conventions sections/claude-md/ DONE
Build a plugin, manifest, components, distribution, versioning sections/plugins/ DONE
Author an agent, frontmatter canon, agent profiles, real production agents sections/agents/ DONE
Configure hooks, hook types, ordering, common bugs sections/hooks/ DONE
Use MCP, when to integrate, propagation issues, debugging sections/mcp/ DONE
Avoid common mistakes — synthesis across all topics sections/antipatterns/ DONE

When the user's question touches multiple sections, prefer the section with the most concrete answer; cite the others.

Loading procedure

  1. Identify the section via the table above.
  2. Read sections/<section>/_index.md — it routes to the narrowest content file.
  3. Load that content file only. Do not pre-load all files in a section.
  4. Answer the user's question, citing the file path (e.g., "see sections/claude-md/hierarchy.md").

Section status

All six sections are authored (DONE) — claude-md, plugins, agents, hooks, mcp, antipatterns. There are no stubs; every router row resolves to real content (RFC-005..009 closed). If a future section is ever added as a stub, tell the user it is not yet authored, cite its scoping RFC, and offer the closest DONE section as a partial answer.

Cross-section references

When a content file references another section, it uses relative paths (e.g., ../plugins/manifest.md). Follow them if the target is DONE; otherwise note the stub status.

Output style

Match the user's language (Russian or English). Keep answers practical — show the rule first, then the example, then the trap. Prefer one strong example over three weak ones.

Install via CLI
npx skills add https://github.com/ForgePlan/marketplace --skill cc-best
Repository Details
star Stars 2
call_split Forks 0
navigation Branch main
article Path SKILL.md
More from Creator