Feature Comparison
| High-value page | Primary intent | Best next action |
|---|---|---|
| Claude Code Custom Commands | Generate reusable command markdown files | Use the generator and publish a small template library. |
| Claude Code Hooks | Automate checks around lifecycle events | Use the JSON generator, then document a debugging checklist. |
| Best MCP Servers for Claude Code | Choose integrations by developer workflow | Compare filesystem, GitHub, Playwright, Context7, database, and design servers. |
| Context7 API Key | Configure docs context for Claude Code, Cursor, and Codex | Create a key, store it safely, then test the MCP connection. |
| Claude Code Slash Commands | Copy prompt templates for review, PRD, refactor, tests, security, changelog, and commits | Link slash templates back to custom commands and hooks. |
Cluster Map
Treat Claude Code Tools as the top-level hub, then send each high-intent search to the page that matches what the developer is trying to do right now.
Build Order
Prioritize pages that have both copy-and-paste utility and commercial intent. Custom commands and hooks deserve the most visible placement because they naturally support generators, templates, and upgrade paths into team workflows.
- P0: Claude Code custom commands as a generator plus template library.
- P0: Claude Code hooks as examples, JSON generator, and debugging checklist.
- P0: Best MCP servers for Claude Code as a comparison directory.
- P1: Context7 API key as a configuration and troubleshooting guide.
- P1: Claude Code slash commands as a command template directory.
Internal Link Rules
Every page in the cluster should link to the tool page and at least two sibling templates. This helps searchers move from explanation to generation without returning to search results.
Hub -> custom commands generator Hub -> hooks generator Hub -> MCP comparison Hub -> Context7 setup Custom commands <-> slash commands Hooks guide <-> hooks generator MCP comparison <-> Context7 API key
Monetizable Intent
These searches are valuable because developers are already trying to configure a tool, fix a workflow, or choose integrations. The strongest pages should include copyable config, a generator CTA, and a short troubleshooting path.
FAQ
What should I build first for a Claude Code tools cluster?
Build the custom commands generator and hooks generator first, then support them with slash command templates, MCP server comparisons, and Context7 API key setup.
Should Claude Code hooks and custom commands be separate pages?
Yes. The intent is different: hooks are lifecycle automation, while custom commands are user-triggered reusable prompts.
Where should Context7 fit in the cluster?
Put Context7 under MCP and documentation workflows, then link it from best MCP servers, Claude Code MCP, and troubleshooting pages.