plugin-settings

Store per-project plugin settings using YAML frontmatter in a local Markdown file at the project root. This pattern ensures configuration travels with code while enabling consistent behavior across local development and CI workflows.

The best way to configure Claude plugins with YAML frontmatter is creating a dedicated configuration file in the project root. Structured settings go in the YAML frontmatter, while prompts or supplementary context go in the Markdown body.

Yes, you can use a Markdown body for plugin prompts alongside YAML frontmatter settings. This pattern allows you to place structured configuration in the frontmatter fields and use the Markdown body for prompts or supplementary context.

Persist plugin state across hooks, commands, and agents by reading, updating, and writing to a local Markdown configuration file with YAML frontmatter. This dedicated root location maintains consistent plugin state throughout project workflows.

Per-project plugin configuration requires a dedicated root location, specifically a file named .claude/plugin-name.local.md at the project root. This ensures the plugin settings remain local to the project and travel with the code.

YAML frontmatter provides structured settings fields while the Markdown body offers space for prompts or supplementary context, combining configuration and context in one local file. This dual structure supports activation, customization, and consistent behavior better than standard config files.