Do I need to commit these files to Git?

No, these files are intended to be project-local and user-specific. You should add .claude/*.local.md to your project's .gitignore file.

How do I parse these files in a shell script?

The skill includes optimized sed and awk patterns to help you extract both the YAML frontmatter fields and the Markdown body within your Bash hooks.

Where are the settings files stored?

Settings are stored in the project root directory under the .claude/ folder, following the naming convention plugin-name.local.md.

Can I use this for agent state management?

Yes, it is specifically designed to store agent metadata, current task progress, and coordination details that need to persist across multiple commands.

How do I apply changes made to a settings file?

Because Claude Code hooks and configurations are typically loaded at the start of a session, you must restart your Claude Code session for changes to take effect.

Claude Plugin Settings Pattern

Name: Claude Plugin Settings Pattern
Author: Microck

byMicrock

•

개발자 도구

Implements a standardized pattern for project-specific plugin configuration and state management using YAML frontmatter and Markdown.

소개

This skill provides a robust framework for creating user-configurable Claude Code plugins by utilizing the .claude/plugin-name.local.md file pattern. It enables developers to store structured configuration data and extended markdown prompts within the project directory while maintaining git-ignored local state. By standardizing how hooks, commands, and agents read per-project settings, it facilitates flexible automation, environment-specific behavior, and persistent agent state management without hardcoding values or modifying core plugin files.

주요 기능

Markdown body integration for dynamic prompt context and instructions
81 GitHub stars
Bash-ready parsing patterns for reading settings within hooks and scripts
YAML frontmatter support for structured configuration keys and values
Standardized .claude/*.local.md file structure for project-specific settings
Integrated lifecycle management via .gitignore for environment-specific overrides

사용 사례

Defining project-level validation rules, strictness levels, and file size limits for automation tools
Enabling or disabling specific plugin hooks on a per-project basis without configuration changes
Managing state for multi-agent swarms, such as tracking task IDs and session coordinators

소개

주요 기능

Markdown body integration for dynamic prompt context and instructions
81 GitHub stars
Bash-ready parsing patterns for reading settings within hooks and scripts
YAML frontmatter support for structured configuration keys and values
Standardized .claude/*.local.md file structure for project-specific settings
Integrated lifecycle management via .gitignore for environment-specific overrides

사용 사례

Defining project-level validation rules, strictness levels, and file size limits for automation tools
Enabling or disabling specific plugin hooks on a per-project basis without configuration changes
Managing state for multi-agent swarms, such as tracking task IDs and session coordinators