plugin-settings

Store per-project plugin settings by writing YAML frontmatter in a claude/plugin-name.local.md file. This pattern allows per-repo customization with structured defaults while remaining Git-ignored for safe local configuration.

Manage per-repo configuration using claude/plugin-name.local.md files. These files are locally ignored by Git, allowing you to safely store structured YAML frontmatter and Markdown body context without exposing sensitive settings.

Apply YAML frontmatter in claude/plugin-name.local.md to control plugin enablement, modes, and state. The skill provides safe parsing and validation guidance to ensure fields drive behavior correctly during development and testing.

The configuration pattern provides documented read, update, and reload workflows for development, CI, and runtime hooks. However, when initially creating the claude/plugin-name.local.md file, you must restart Claude Code to load the settings.

Yes, you can use this local Markdown configuration pattern in CI environments. The skill supports lifecycle scenarios including reading, updating, and reloading settings during development, testing, and deployment workflows.

Local Markdown settings files are ignored by Git, meaning configurations are local to each repository instance and not shared across teams. You must manage defaults and secure handling manually to maintain disciplined config patterns.