Do settings changes apply immediately?

Changes to .local.md files usually require a Claude Code restart because hooks and plugin configurations are initialized at the start of a session.

What is the .local.md file pattern?

It is a convention for storing project-specific configuration files in the .claude/ directory. The .local suffix ensures these files are ignored by version control.

Can I read these settings from a shell script?

Yes, the skill provides specific Bash patterns using sed and grep to extract YAML frontmatter values directly into variables for use in hooks.

How do I handle default values?

Best practices involve implementing a fallback in your scripts that checks for the existence of the settings file and applies default constants if the file is missing.

Plugin Configuration Manager

Name: Plugin Configuration Manager
Author: chrismcgraw60

bychrismcgraw60

Developer Tools

Manages per-project plugin settings and state using a standardized YAML and Markdown file pattern.

About

The Plugin Configuration Manager skill provides a robust architectural pattern for storing and retrieving plugin-specific settings via local files in the .claude/ directory. By utilizing a hybrid format of YAML frontmatter for structured data and Markdown for descriptive context, it enables developers to create highly configurable plugins that adapt to individual project needs. This skill is essential for managing plugin states, toggleable hooks, and agent instructions without cluttering global configurations or committing sensitive local data to version control.

Key Features

Support for hybrid YAML frontmatter and rich Markdown content
Agent-specific state management and instruction injection
Bash-compatible parsing patterns for reading settings in hooks
Security-focused design that prevents local settings from being committed to Git
Standardized .local.md file structure for project-specific configurations
0 GitHub stars

Use Cases

Managing multi-agent coordination by storing shared state in local files
Toggling specific plugin hooks on or off per project without code changes
Defining custom validation thresholds and environment-specific plugin behaviors

About

Key Features

Support for hybrid YAML frontmatter and rich Markdown content
Agent-specific state management and instruction injection
Bash-compatible parsing patterns for reading settings in hooks
Security-focused design that prevents local settings from being committed to Git
Standardized .local.md file structure for project-specific configurations
0 GitHub stars

Use Cases

Managing multi-agent coordination by storing shared state in local files
Toggling specific plugin hooks on or off per project without code changes
Defining custom validation thresholds and environment-specific plugin behaviors