What problem does it solve?
Plugin Settings solves the problem of making AI-assisted developer plugins controllable and stateful without editing plugin code, by using a user-local, per-project settings file.
Core Features & Use Cases
- Per-project plugin configuration & state stored in
.claude/plugin-name.local.md so behavior can vary by repository.
- YAML frontmatter-driven settings (e.g.,
enabled, validation modes, limits) that hooks, commands, and agents can read deterministically.
- Operational patterns for safe parsing and defaults, including frontmatter extraction, enabled/disabled gating, and documenting the restart requirement.
What is it for?
Use this skill when you need to store user-configurable plugin behavior such as enabling/disabling a plugin, setting strict vs standard validation, specifying retry limits, or coordinating multi-agent workflows through shared state in the project.
Quick Start
Ask: "Create a .claude/my-plugin.local.md file for this project with enabled: true and a strict_mode: false setting, and explain how a hook should read the YAML frontmatter to decide whether to run."