Guide for configuring Claude Code optimally. Use when users ask about: CLAUDE.md structure, plugin architecture, skill patterns, hooks, MCP integration, settings.json, slash commands, or Claude Code best practices.
/plugin marketplace add GGPrompts/TabzChrome/plugin install codex@tabz-chromeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/claude-md.mdreferences/commands.mdreferences/hooks.mdreferences/mcp.mdreferences/plugin-structure.mdreferences/settings.mdreferences/skills.mdHelp users configure Claude Code for optimal development workflows.
| Task | Location/Command |
|---|---|
| Project instructions | CLAUDE.md (root) |
| Settings | .claude/settings.json or ~/.claude/settings.json |
| Slash commands | .claude/commands/*.md |
| Skills | .claude/skills/<name>/SKILL.md |
| Hooks | .claude/settings.local.json |
| MCP servers | .mcp.json or .claude/mcp.json |
| Plugins | plugins/<name>/plugin.json |
The CLAUDE.md file provides project context to Claude. Keep it concise (<500 lines).
# Project Name
Brief description of what this project does.
## Architecture
Key directories, patterns, and data flow.
## Development Rules
### ALWAYS
- Critical patterns to follow
### NEVER
- Anti-patterns to avoid
## Quick Reference
| Command | Purpose |
|---------|---------|
| `npm run dev` | Start development |
| `npm test` | Run tests |
## Key Files
| File | Purpose |
|------|---------|
| `src/index.ts` | Entry point |
Best practices:
For detailed CLAUDE.md patterns: See references/claude-md.md
Plugins package commands, skills, hooks, and MCP servers together.
plugins/my-plugin/
├── plugin.json # Metadata (required)
├── commands/ # Slash commands
│ └── my-command.md
├── skills/ # Agent skills
│ └── my-skill/
│ └── SKILL.md
├── agents/ # Subagent definitions
│ └── my-agent.md
└── hooks/ # Hook scripts
└── pre-tool.sh
plugin.json:
{
"name": "my-plugin",
"version": "1.0.0",
"description": "Plugin description"
}
For plugin development guide: See references/plugin-structure.md
Skills extend Claude's capabilities with domain-specific knowledge.
.claude/skills/my-skill/
├── SKILL.md # Instructions (required)
├── references/ # Detailed docs (loaded on demand)
├── scripts/ # Executable code
└── assets/ # Templates
SKILL.md structure:
---
name: my-skill
description: "When to trigger this skill"
---
# Skill Name
Brief description.
## When to Use
Specific activation criteria.
## Instructions
Step-by-step guidance.
## Quick Reference
For detailed X: See `references/x.md`
Progressive disclosure: Keep SKILL.md concise (<200 lines). Put detailed documentation in references/ directory.
For skill development patterns: See references/skills.md
Hooks execute shell commands in response to Claude Code events.
Configure in .claude/settings.local.json:
{
"hooks": {
"PreToolUse": [
{
"matcher": "Bash",
"hooks": ["./scripts/validate-bash.sh"]
}
],
"PostToolUse": [
{
"matcher": "Write",
"hooks": ["prettier --write $CLAUDE_FILE_PATH"]
}
],
"UserPromptSubmit": [
{
"hooks": ["./scripts/log-prompt.sh"]
}
]
}
}
Hook types:
PreToolUse - Before tool execution (can block)PostToolUse - After tool executionUserPromptSubmit - When user submits promptEnvironment variables available:
$CLAUDE_TOOL_NAME - Tool being called$CLAUDE_FILE_PATH - File path (for file tools)For hook patterns and examples: See references/hooks.md
Model Context Protocol connects Claude to external tools and services.
Configure in .mcp.json:
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/allowed/path"]
},
"github": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": {
"GITHUB_TOKEN": "${GITHUB_TOKEN}"
}
}
}
}
Common MCP servers:
@modelcontextprotocol/server-filesystem - File access@modelcontextprotocol/server-github - GitHub integration@modelcontextprotocol/server-postgres - Database queries@modelcontextprotocol/server-puppeteer - Browser automationFor MCP configuration guide: See references/mcp.md
Project settings (.claude/settings.json):
{
"model": "sonnet",
"maxTokens": 8192,
"thinking": {
"enabled": true,
"budget": 10000
}
}
Model aliases:
sonnet - Balanced (default)opus - Complex taskshaiku - Fast, simple tasksFor full settings reference: See references/settings.md
Create custom commands in .claude/commands/:
.claude/commands/deploy.md:
---
description: Deploy to production
---
Run the deployment pipeline:
1. Run tests: `npm test`
2. Build: `npm run build`
3. Deploy: `./scripts/deploy.sh`
Verify deployment succeeded and report status.
Invoke with: /deploy
Arguments: Use $ARGUMENTS for user input
---
description: Create a component
---
Create a React component named $ARGUMENTS in src/components/.
For command patterns: See references/commands.md
.claude/settings.json - Model and token settings.mcp.json - External tool integrations.claude/commands/ - Frequently used workflows.claude/skills/ - Domain-specific knowledgeAuto-format on write:
{
"hooks": {
"PostToolUse": [
{"matcher": "Write", "hooks": ["prettier --write $CLAUDE_FILE_PATH"]}
]
}
}
Validate before bash:
{
"hooks": {
"PreToolUse": [
{"matcher": "Bash", "hooks": ["./scripts/validate-command.sh"]}
]
}
}
.mcp.json - use ${ENV_VAR} syntaxLoad these for detailed guidance:
| Topic | Reference |
|---|---|
| CLAUDE.md patterns | references/claude-md.md |
| Plugin development | references/plugin-structure.md |
| Skill patterns | references/skills.md |
| Hook configuration | references/hooks.md |
| MCP servers | references/mcp.md |
| Settings reference | references/settings.md |
| Command patterns | references/commands.md |
| Aspect | Codex | Claude Code |
|---|---|---|
| Provider | OpenAI | Anthropic |
| Config file | ~/.codex/config.toml | ~/.claude/settings.json |
| Skills | ~/.codex/skills/ | .claude/skills/ + plugins |
| MCP | config.toml sections | .mcp.json |
| Agents | N/A | Plugin agents |
| Hooks | N/A | Pre/Post tool hooks |
| Commands | N/A | .claude/commands/ |
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.