plugin-settings

To configure plugin settings without modifying code, define your user-specific options using YAML frontmatter in a local markdown file. This approach separates configuration from the core plugin code, allowing you to tailor plugin behavior safely.

The best way to manage YAML frontmatter for plugin customization is to structure your configuration variables within the frontmatter block of a markdown file. This method provides a structured format for settings while allowing additional markdown context for documentation.

To set up a local configuration file for a code review plugin, create a markdown file in the `.Codex` directory named `plugin-name.local.md`. Place your YAML frontmatter settings inside this file to manage the plugin options without touching the code.

Yes, this plugin configuration approach works with both YAML and markdown by parsing YAML frontmatter for structured settings and the markdown body for additional context. This combination allows for structured configuration alongside human-readable documentation.

You use YAML frontmatter for plugin configuration instead of editing code directly to reduce manual configuration errors and avoid modifying source files. This separation allows users to safely update and manage plugin behavior without risking the core codebase.