plugin-settings

Per-project settings for Claude Code plugins are stored using YAML frontmatter in a local .claude/plugin-name.local.md file. This approach standardizes configuration storage and prevents drift between different repositories by maintaining local config state.

Configuring per-project plugin behavior in Claude Code is best handled by defining YAML frontmatter toggles like enabled, mode, and settings within a local .claude file. This pattern provides clear templates for hooks, commands, and agents to read and apply settings.

YAML frontmatter settings for Claude Code hooks are read and applied at runtime by parsing the local .claude/plugin-name.local.md file. This mechanism maintains per-project state and defaults, allowing commands and agents to customize behavior dynamically.

Yes, Claude Code supports local configuration files for per-repo plugin customization through the .claude/plugin-name.local.md pattern. This local config file uses YAML frontmatter to define per-project toggles and settings, ensuring plugin behavior is customized per repository.

Plugin configuration drift between projects occurs when settings are not standardized locally. Using YAML frontmatter in a per-project .claude/plugin-name.local.md file solves this by providing a consistent configuration pattern for storing and reading per-repo settings.

Yes, YAML frontmatter can manage per-project state and defaults for Claude Code commands by storing configuration in .claude/plugin-name.local.md. This allows commands and agents to parse frontmatter at runtime and apply customized per-project behavior.