plugin-settings

You can manage per-project plugin configurations by creating a `.claude/plugin-name.local.md` file in your project root, using YAML frontmatter for structured settings and markdown for additional context without altering core code.

The best way to store local state and settings is using the `.claude/plugin-name.local.md` file pattern, which leverages YAML frontmatter for structured configuration data and markdown body for contextual documentation.

Yes, you can use YAML frontmatter in your `.claude/plugin-name.local.md` files to define structured plugin settings like `enabled: true` or `mode: strict` on a per-project basis.

The `.claude/plugin-name.local.md` pattern works by storing YAML frontmatter settings and markdown context locally in the project directory, enabling plugin behavior customization and state persistence across projects without global changes.

You need a local markdown file for project specific plugin configuration when you want to customize plugin behavior, such as setting a linter to strict mode or storing task progress, independently for each project.

No, this plugin settings approach requires no external dependencies, relying solely on the standard `.claude/plugin-name.local.md` file pattern with YAML frontmatter and markdown for local state management.