Plugin Settings

Per-project plugin configuration stored in YAML frontmatter and markdown files within the .claude/ directory. Plugins can store user-configurable settings and state in .claude/plugin-name.local.md files within the project directory. This pattern uses YAML frontmatter for structured configuration and markdown content for prompts or additional context. Key characteristics: .claude/my-plugin.local.md: Pattern: Check existence and parse frontmatter See examples/read-settings-hook.sh for complete working example. Commands can read settings files to customize behavior: Agents can reference settings in their instructions: String fields: Boolean fields: Numeric fields: Extract content after second --- : Use settings file to control hook activation: Use case: Enable/disable hooks without editing hooks.json (requires restart). Store agent-specific state and configuration: .claude/multi-agent-swarm.local.md: Read from hooks to coordinate agents: .claude/my-plugin.local.md: Use in hooks or commands: Commands can create settings files: Provide template in plugin README: ✅ DO: ❌ DON'T: Always add to .gitignore : Document this in plugin README. Provide sensible defaults when settings file doesn't exist: Validate settings values: Important: Settings changes require Claude Code restart. Document in your README: Hooks cannot be hot-swapped within a session.