What problem does it solve? Claude Code plugins often need user-configurable behavior and persistent state, but there is no built-in settings mechanism. This Skill documents the .claude/plugin-name.local.md pattern, letting plugin developers store per-project configuration in YAML frontmatter plus markdown content that hooks, commands, and agents can read. ## Core Features & Use Cases - Settings File Pattern: Defines the .claude/plugin-name.local.md structure with YAML frontmatter for structured config and a markdown body for prompts or context. - Bash Parsing Techniques: Provides sed, grep, and awk recipes for extracting frontmatter fields and markdown bodies, including quote handling, defaults, and validation. - Real-World Examples: Analyzes how the multi-agent-swarm and ralph-loop plugins use settings files for agent coordination state and loop iteration control. - Use Case: You are building a validation hook plugin and want users to toggle strict mode per project. Create a .claude/my-plugin.local.md template, parse the enabled and strict_mode fields in your hook, and let users change behavior without editing hooks.json. ## Quick Start Ask the AI to add a configurable settings file to your plugin using the .claude/plugin-name.local.md pattern with an enabled flag and parsing logic in the hook.
