plugin-settings

Per-project plugin configurations are standardized by storing and retrieving settings using YAML frontmatter within local markdown files. This approach isolates project-specific behavior customizations for hooks, commands, and agents without modifying global settings.

You isolate plugin settings by storing project-specific configurations in .claude/plugin-name.local.md files. These local state files ensure configurations remain isolated and can be git-ignored, allowing distinct behaviors like strict validation for security-sensitive projects.

Yes, you need standard Unix utilities like sed, grep, and awk to parse YAML frontmatter from local markdown files. This Skill requires these command-line tools to extract and validate configuration fields from the local state files.

The best way to standardize plugin behavior customization is using a file-based configuration pattern with YAML frontmatter. This provides a clean, readable format to define plugin settings, state, and behavior flags consistently across different projects.

You create a local configuration file for your plugin by defining YAML frontmatter within a markdown file located at .claude/plugin-name.local.md. This file persists enabled states and behavior flags specifically for that project.