Plugin Settings

You can manage per-project plugin configurations by creating `.claude/plugin-name.local.md` files at your project root, using YAML frontmatter for structured settings and markdown for context without altering core plugin code.

Storing user-specific plugin state locally is best achieved using `.claude/plugin-name.local.md` files with YAML frontmatter, ensuring individual configurations are kept separate and not committed to version control.

You can read dynamic plugin settings from bash scripts and commands by storing the desired state in local markdown files, allowing the plugin behavior to adapt based on the parsed YAML frontmatter values.

Yes, you can adjust a linter's `strict_mode` per project by creating a `.claude/linter.local.md` file with YAML frontmatter, enabling project-specific configuration overrides without changing the plugin itself.

To ensure local project configurations are ignored by version control, use the `.claude/plugin-name.local.md` file pattern, which is explicitly designed to keep user-specific settings and state uncommitted.

You need YAML frontmatter in markdown files for plugin settings when you want to store structured key-value configurations alongside additional context or documentation for flexible, context-aware plugin behavior.