What problem does it solve?
This Skill eliminates the hassle of managing per-project, user-specific configuration for Claude Code plugins by providing a standardized, gitignored file pattern that avoids hardcoding values or committing sensitive settings to version control.
Core Features & Use Cases
- Standardized Settings Pattern: Documents the .claude/plugin-name.local.md format that uses YAML frontmatter for structured configuration and a markdown body for freeform context or prompts.
- Cross-Context Parsing: Includes ready-to-use bash patterns for reading settings files from hooks, commands, and agents, with support for extracting boolean, numeric, and string fields.
- Production-Ready Guardrails: Provides validation techniques, atomic update patterns, security best practices for sanitizing input and preventing path traversal, and real-world examples from popular plugins like multi-agent-swarm and ralph-wiggum.
- Use Case: A developer building a Claude Code plugin for code validation can let users set per-project validation strictness, file size limits, and allowed file extensions via a simple .local.md file instead of modifying plugin code.
Quick Start
Use this Skill to implement user-configurable per-project settings for your Claude Code plugin by adopting the .claude/plugin-name.local.md file pattern with YAML frontmatter and bash parsing logic.