Do I need to restart Claude Code after changing settings?

Yes, because hooks and certain plugin configurations are loaded at the start of a session, a restart is required for changes to take effect.

How do I read these settings in a bash hook?

You can use standard shell utilities like sed and grep to extract the YAML frontmatter between the triple-dash markers and parse individual configuration fields.

Should I commit these settings files to Git?

No, these files are intended to be user-local. It is recommended to add .claude/*.local.md to your project's .gitignore file.

Where are these plugin settings stored?

Settings are stored in the .claude/ directory of your project root, specifically using the naming convention plugin-name.local.md.

Plugin Settings Manager

Name: Plugin Settings Manager
Author: nordeim

bynordeim

Developer Tools

Standardizes project-level plugin configuration and state management using YAML frontmatter and Markdown files.

About

The Plugin Settings skill implements a robust pattern for managing Claude Code plugin configurations and persistent states through .claude/plugin-name.local.md files. By leveraging YAML frontmatter for structured data and Markdown for extended context, it allows developers to create highly configurable, project-specific plugin behaviors without hardcoding values. This pattern is particularly useful for toggling hooks, managing multi-agent session states, and defining validation thresholds that vary between different codebases.

Key Features

YAML frontmatter parsing for structured plugin metadata
Project-level state persistence for multi-agent coordination
Bash-compatible parsing techniques for hooks and commands
Standardized .claude/plugin-name.local.md configuration pattern
0 GitHub stars
Markdown body support for dynamic prompts and context

Use Cases

Enabling or disabling specific plugin hooks on a per-project basis
Defining custom validation levels and file size limits for specialized dev tools
Storing agent-specific state such as task progress or PR identifiers

About

Key Features

YAML frontmatter parsing for structured plugin metadata
Project-level state persistence for multi-agent coordination
Bash-compatible parsing techniques for hooks and commands
Standardized .claude/plugin-name.local.md configuration pattern
0 GitHub stars
Markdown body support for dynamic prompts and context

Use Cases

Enabling or disabling specific plugin hooks on a per-project basis
Defining custom validation levels and file size limits for specialized dev tools
Storing agent-specific state such as task progress or PR identifiers