What problem does it solve?
This Skill helps you store and read per-project plugin configuration in a simple Markdown file instead of scattering settings across scripts, hooks, and ad hoc notes.
Core Features & Use Cases
- Project-local configuration: Keep plugin settings in a .claude/plugin-name.local.md file with YAML frontmatter and a readable Markdown body.
- State and behavior control: Toggle features, store iteration or task state, and adapt plugin behavior based on user-defined values.
- Parsing and validation: Read frontmatter fields, extract body content, validate booleans and numeric limits, and update settings safely with atomic file writes.
- Use Case: A team enables a plugin only for one repository, sets strict validation mode, and stores task context directly in the file so hooks and commands can respond consistently.
Quick Start
Create a .claude/plugin-name.local.md file with YAML frontmatter and a markdown body, then restart Claude Code so the plugin can load the new settings.