plugin-settings

To manage per-project plugin configurations, create a `.claude/plugin-name.local.md` file in your project root with YAML frontmatter. Restart Claude Code to apply the settings, ensuring consistent behavior management for hooks, commands, and agents.

Storing project-specific plugin settings in local markdown files with YAML frontmatter isolates configuration from global state. This pattern prevents global pollution by keeping settings-driven logic strictly tied to the current project directory.

You can use YAML frontmatter to toggle plugin behavior by defining configuration keys within the frontmatter block. The plugin then parses this structured configuration to enable or disable features, such as strict validation modes, for that specific project.

Yes, Claude Code supports version-controlled settings by storing plugin configurations as YAML frontmatter in local markdown files. This approach makes settings easily accessible to hooks, commands, and agents while remaining version-controlled.

Yes, you can use markdown files for state management by standardizing configuration storage with YAML frontmatter. This provides robust parsing patterns that facilitate settings-driven logic across multiple hooks, commands, and agents consistently.

Local plugin settings in YAML frontmatter may not apply if Claude Code was not restarted after modifying the `.claude/plugin-name.local.md` file. Restarting the application ensures the new per-project configurations are properly loaded.