plugin-settings

You can manage per-project plugin configurations by storing settings as YAML frontmatter within local markdown files. This isolates project state and prevents global configuration pollution.

Storing plugin state in markdown files is best achieved by embedding YAML frontmatter. This provides clean, machine-readable structured configuration with robust parsing for boolean, numeric, and string settings.

To parse YAML frontmatter with default values and validation, implement parsing logic that extracts boolean, numeric, and string settings from markdown files. This ensures configurations adhere to defined validation rules.

You need sed, awk, grep, and jq to standardize plugin configuration parsing. These utilities provide the text processing capabilities required to extract and manipulate YAML frontmatter from local markdown files.

You can define custom validation rules for agents in a local markdown file by using YAML frontmatter. The plugin automatically reads this structured configuration and applies it to its execution logic.

Your plugin configuration may not apply if the YAML frontmatter parsing fails validation or lacks defined default values. Ensure the local markdown file correctly formats boolean, numeric, and string settings for the plugin to read.