plugin-settings

What problem does it solve?

Plugins often need user-configurable settings or to persist state on a per-project basis, but lack a standardized, user-friendly mechanism. This Skill provides a robust pattern for managing plugin settings, making your plugins more adaptable and reducing manual configuration effort.

Core Features & Use Cases

• Project-Specific Configuration: Store settings and state in .claude/plugin-name.local.md files, keeping configurations isolated per project.
• YAML Frontmatter & Markdown Body: Use structured YAML for settings and the Markdown body for prompts or additional context, offering flexibility.
• Bash Parsing Techniques: Learn to efficiently read and extract configuration fields and content using standard bash tools.
• Configuration-Driven Behavior: Implement logic in hooks, commands, and agents that dynamically adapts based on loaded settings.
• Use Case: Enable/disable specific plugin features per project, set different validation levels for development vs. production, or manage the state of multi-agent workflows.

Quick Start

Explain how to create a .claude/my-plugin.local.md file to store a boolean 'enabled' setting for my plugin.