Where should I store plugin-specific settings?

Plugin settings should be stored in the project root directory at .claude/plugin-name.local.md.

What is the benefit of using Markdown with YAML frontmatter?

It allows you to store structured data (YAML) alongside unstructured context or prompts (Markdown) in a single, human-readable file.

Do settings changes apply immediately in Claude Code?

No, changes to settings files require a restart of Claude Code for hooks to recognize and load the new configuration.

How do I parse these settings in a Bash script?

You can use sed to extract content between triple-dash separators and grep to isolate specific YAML key-value pairs.

Should .local.md files be committed to version control?

No, these files are intended for local user-specific configuration and should be added to your .gitignore file.

Plugin Settings Pattern

Name: Plugin Settings Pattern
Author: iButters

byiButters

•

Developer Tools

Standardizes per-project configuration for Claude Code plugins using YAML frontmatter and markdown state files.

About

The Plugin Settings skill provides a robust architectural pattern for Claude Code plugins to store user-configurable settings and persistent state without cluttering global configurations. By utilizing a standardized .claude/plugin-name.local.md file format, developers can implement project-specific behaviors, enable or disable hooks dynamically, and manage agent-specific data across sessions. This skill documents implementation strategies for reading configuration via Bash scripts, CLI commands, and AI agents, ensuring that plugin behavior remains flexible, secure, and easy for end-users to customize.

Key Features

1 GitHub stars
Per-project configuration and persistent state management
Pattern for reading settings from Bash hooks and CLI tools
Standardized .local.md file structure with YAML frontmatter
Best practices for security, validation, and Git integration
Dynamic activation/deactivation of plugin-specific hooks

Use Cases

Enabling or disabling specific plugin hooks without modifying core JSON files
Storing project-specific validation levels, API keys, or processing modes
Managing state for multi-agent workflows and long-running automated tasks

About

Key Features

1 GitHub stars
Per-project configuration and persistent state management
Pattern for reading settings from Bash hooks and CLI tools
Standardized .local.md file structure with YAML frontmatter
Best practices for security, validation, and Git integration
Dynamic activation/deactivation of plugin-specific hooks

Use Cases

Enabling or disabling specific plugin hooks without modifying core JSON files
Storing project-specific validation levels, API keys, or processing modes
Managing state for multi-agent workflows and long-running automated tasks