Where are these settings files stored?

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

Should I commit these settings files to Git?

No, these are intended for local user configuration and should be added to your .gitignore to prevent committing local state or environment-specific preferences.

Do I need to restart Claude Code after changing settings?

Yes, because hooks cannot be hot-swapped within an active session, a restart is typically required for new configurations to take effect.

Can I use these settings in custom Bash hooks?

Yes, this skill provides specific shell patterns using sed and awk to extract YAML fields and Markdown content directly within Bash script hooks.

Plugin Settings Manager

Name: Plugin Settings Manager
Author: Activer007

byActiver007

Developer Tools

Standardizes per-project plugin configuration using YAML-frontmatter-enhanced markdown files within the .claude directory.

About

This skill implements a robust pattern for managing plugin-specific settings and state within Claude Code projects. By utilizing the .claude/plugin-name.local.md file structure, it allows developers and users to define granular configurations—such as execution modes, API limits, or agent instructions—that remain local to the project. The skill provides clear patterns for parsing YAML frontmatter in Bash hooks and Markdown prompts in agents, enabling highly adaptable and context-aware automation workflows without requiring global configuration changes.

Key Features

Pre-built Bash parsing techniques for extracting settings within hooks
0 GitHub stars
Guidelines for Git-safe practices and session-based reloading
Standardized .claude/*.local.md file pattern for local-only configuration
Hybrid YAML frontmatter and Markdown body structure for structured data and rich prompts
State management capabilities for coordinating multi-agent workflows

Use Cases

Storing persistent state for long-running agent loops or multi-step tasks
Providing project-specific prompts and validation rules without editing source code
Enabling or disabling specific plugin hooks on a per-project basis

About

Key Features

Pre-built Bash parsing techniques for extracting settings within hooks
0 GitHub stars
Guidelines for Git-safe practices and session-based reloading
Standardized .claude/*.local.md file pattern for local-only configuration
Hybrid YAML frontmatter and Markdown body structure for structured data and rich prompts
State management capabilities for coordinating multi-agent workflows

Use Cases

Storing persistent state for long-running agent loops or multi-step tasks
Providing project-specific prompts and validation rules without editing source code
Enabling or disabling specific plugin hooks on a per-project basis