What problem does it solve? Claude Code plugins often need user-configurable, per-project settings, but there is no built-in mechanism for storing plugin state outside of hooks.json. This Skill documents the .claude/plugin-name.local.md pattern so plugin authors can read and write structured configuration without editing global config files. ## Core Features & Use Cases - Settings File Pattern: Store plugin configuration in .claude/plugin-name.local.md files combining YAML frontmatter for structured fields and a markdown body for prompts or instructions. - Parsing Recipes: Provides bash snippets using sed, grep, and awk to extract frontmatter fields and markdown body content from hooks, commands, and agents. - Real-World Examples: Includes patterns from multi-agent-swarm (agent state coordination) and ralph-loop (iteration tracking with completion promises), plus best practices for gitignore, defaults, validation, and security. - Use Case: You are building a Claude Code plugin whose hook should only run when enabled per project. Create a .claude/my-plugin.local.md file with an enabled flag, and use the quick-exit parsing pattern in your hook script to check it. ## Quick Start Ask the AI to create a .claude/my-plugin.local.md settings file with YAML frontmatter and show a bash hook that reads the enabled flag from it.
