plugin-settings

Store per-project plugin configuration by creating a local Markdown file with YAML frontmatter. This pattern isolates project-specific settings in a dedicated file, enabling predictable plugin behavior without modifying global configurations.

Managing local YAML settings is best handled by storing them in a gitignored Markdown file with a YAML frontmatter block. This prevents accidental commits of sensitive information while keeping structured settings and contextual prompts together.

Apply project-specific settings during hook execution by reading and validating the local YAML frontmatter configuration file. The Skill provides templates and workflows to safely parse these settings before triggering command workflows or agent coordination.

Plugin configuration supports safe-edit workflows by providing templates and best practices for modifying local Markdown files. This ensures structured YAML frontmatter settings are validated and applied correctly without corrupting the file.

Use YAML frontmatter in a Markdown file for plugin settings to separate structured configuration data from descriptive context. This approach keeps project state isolated and predictable while preventing sensitive information from being committed to version control.

You can isolate plugin behavior across projects by using a dedicated local configuration file. Each project maintains its own Markdown file with YAML frontmatter, ensuring that settings, prompts, and hook executions remain independent and predictable.