What problem does it solve?
This Skill enables per-project plugin configuration by documenting a reusable YAML frontmatter pattern that stores plugin settings in a .claude/plugin-name.local.md file. It guides teams on how to manage per-project state, enablement, and prompts via a local settings file.
Core Features & Use Cases
- Per-project configuration files: .claude/plugin-name.local.md with YAML frontmatter and a markdown body used for prompts or notes.
- Frontmatter parsing guidance for hooks and commands to read, validate, and apply settings.
- Templates and examples for creating and reading per-project settings, plus safe, atomic updates to avoid corruption.
- Use Case: A developer enables a plugin for a single project with specific options while keeping a default configuration in other projects.
Quick Start
To create a settings file for your plugin, generate a .claude/plugin-name.local.md with enabled: true, place your default configuration in the frontmatter, add a short body for prompts, and restart Claude Code for changes to take effect.