Plugin Settings

Manage per-project plugin configurations using `.claude/plugin-name.local.md` files. Store structured key-value settings in YAML frontmatter and additional context in the markdown body, ensuring user-specific configurations remain local and untracked by version control.

Yes, you can read settings from bash scripts and commands. This allows dynamic plugin behavior and state persistence by executing scripts to retrieve current configuration values stored within the local project files.

Persist complex agent task state locally by writing it into `.claude/plugin-name.local.md` files. Use the markdown body for context and YAML frontmatter for structured state variables, keeping the data isolated to the current project root.

Configure a linter plugin by creating a `.claude/my-plugin.local.md` file in your project root. Define the specific rulesets and configuration values in the YAML frontmatter to customize the linter behavior for that project.

Yes, the local settings approach uses standard YAML frontmatter for structured key-value data. This integrates seamlessly with existing YAML parsing tools while allowing unstructured documentation in the markdown body.

Use local markdown files instead of global settings to allow customized plugin behavior per project. This prevents altering global configurations and ensures sensitive or user-specific state is not accidentally committed to version control.