claude-code-expert

Create a skill by defining a frontmatter metadata file in the `skills/` directory within `.claude/`, specifying name, description, and parameters. Add your skill logic, then reference it in `settings.json` to enable it in Claude Code.

The `.claude/` directory holds `skills/`, `commands/`, `hooks/`, `docs/`, and `settings.json`. This structure organizes your CLI extensions: skills define reusable logic, commands create slash commands, hooks trigger validation or automation, and docs store documentation files.

Implement hooks in the `hooks/` directory within `.claude/` to trigger validation or automation at specific CLI events. Define hook logic with frontmatter metadata, then configure triggers in `settings.json` to run on command execution or file changes.

Yes, Claude Code supports MCP plugin integration to connect external tools and services. Configure MCP connections in `settings.json` and reference them in skills or commands to enable data exchange with third-party platforms.

settings.json centralizes Claude Code configuration including skill activation, command registration, hook triggers, MCP plugin connections, and environment-specific security settings. Structure it with metadata keys matching your `.claude/` directory organization.

Create slash commands in the `commands/` directory with frontmatter metadata defining command name, description, and parameters. Commands execute skill logic or trigger hooks, enabling quick automation workflows directly from the CLI interface.