Plugin Settings

Store per-project plugin configuration by creating a `.claude/plugin-name.local.md` file at the project root. This file uses YAML frontmatter for structured options and a Markdown body for instructions, ensuring stable behavior across repositories.

Configuring plugin defaults and state persistence per repository is best handled by saving settings in a dedicated local Markdown file. YAML frontmatter stores structured options while the body drives prompts and context during activation.

Apply per-project settings to hooks, commands, and agents by parsing the YAML frontmatter and reading the Markdown body from the local configuration file. This tailors plugin behavior to each specific project during task execution.

Yes, applying per-project plugin configuration requires a restart to ensure settings take effect. The configuration process includes restart guidance because the YAML frontmatter and Markdown body are loaded during plugin activation.

You need YAML frontmatter for plugin configuration when you want to define structured options like enablement, modes, and limits per project. It separates structured settings from instructional text in the Markdown body.