What problem does it solve?
Claude Code plugins often require project-specific configuration that should not be shared across teams or committed to version control, and this skill provides a standardized, safe pattern for managing that per-project plugin state and settings without risking accidental exposure of sensitive data.
Core Features & Use Cases
- Standardized Settings Pattern: Implements the
.claude/plugin-name.local.md convention for user-local, per-project plugin configuration that is automatically excluded from git commits by default.
- Cross-Component Compatibility: Works with hooks, commands, and agents, supporting both structured YAML frontmatter for configuration values and markdown body content for prompts, task descriptions, or additional context.
- Production-Ready Utilities: Includes bash scripts for parsing frontmatter, validating settings file structure, and performing atomic updates, plus comprehensive guides for handling edge cases like quoted values, special characters, and file path security.
- Use Case: A team building a code validation plugin can use this skill to let users set per-project rules (like maximum file size or allowed file extensions) without modifying the plugin's shared source code.
Quick Start
Use the plugin-settings skill to create a .claude/your-plugin.local.md file with your desired plugin configuration for the current project.