skills.rest
DMT123
DMT123COMMUNITY
Explore all skills by this author →
GitHub

plugin-settings

Manage per-project plugin configurations using .claude/plugin-name.local.md files with YAML frontmatter.

Updated Mar 2, 2026
Search Tags:#yaml frontmatter#bash scripting#plugin configuration#per-project#user settings#local.md
One-click install
npx skills add https://github.com/DMT123/claude-skills-collection --skill plugin-settings-dmt123
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/DMT123/claude-skills-collection/tree/main/plugins/plugin-dev/plugin-settings
Command: npx skills add https://github.com/DMT123/claude-skills-collection --skill plugin-settings-dmt123

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a standardized pattern for managing per-project configurations and state for Claude Code plugins, allowing for flexible and user-defined plugin behavior without modifying core plugin code or committing sensitive information.

Core Features & Use Cases

  • Per-Project Configuration: Store settings in .claude/plugin-name.local.md files.
  • YAML Frontmatter: Use YAML for structured settings (e.g., enabled: true, mode: strict).
  • Markdown Body: Include additional context, prompts, or documentation.
  • Hook/Command Integration: Read settings from bash scripts or commands to adapt behavior.
  • Use Case: A linter plugin can have its strict_mode setting defined per project, enabling stricter checks for sensitive codebases and more lenient checks for general development.

Quick Start

Create a .claude/my-plugin.local.md file with your desired settings and restart Claude Code.

Frequently Asked Questions about plugin-settings

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage per-project plugin configurations without modifying core code?▼

Per-project plugin configurations are managed using a `.claude/plugin-name.local.md` file pattern. This stores settings via YAML frontmatter and markdown context, enabling dynamic behavior adaptation without modifying core plugin code.

What is the best way to store local plugin settings that are gitignored?▼

Storing local plugin settings is best achieved using the `.claude/plugin-name.local.md` file pattern. These user-managed files are gitignored and parsed via bash scripts to read YAML frontmatter for structured configuration.

Can I use YAML frontmatter to configure strict mode for a linter plugin per project?▼

Yes, YAML frontmatter supports structured settings like `enabled: true` or `mode: strict` per project. A linter plugin can read these configurations to apply stricter checks for sensitive codebases and lenient checks elsewhere.

How do bash scripts read plugin configuration from local markdown files?▼

Bash scripts read plugin configuration by parsing the `.claude/plugin-name.local.md` file, extracting YAML frontmatter for structured settings and markdown body for context. This enables hook and command integration for dynamic behavior.

Do I need to restart Claude Code after creating a local.md configuration file?▼

Yes, you need to restart Claude Code after creating a `.claude/my-plugin.local.md` file with your desired settings. This ensures the plugin configurations and state are properly loaded and applied to the current project.

What are the limitations of using markdown files for plugin state management?▼

Limitations include the requirement for user-managed files that must be gitignored, and the need for dedicated bash scripts or tools to parse YAML frontmatter, adding parsing overhead to hook and command execution.

Related Skills

Explore More Software Engineering Skills→
zach-sourcezach-source

Plugin Settings

Manage per-project plugin configuration and state via `.claude/plugin-name.local.md` files.

Community
Intermediate
FacuMFacuM

plugin-settings

Manage per-project plugin configurations using .local.md files with YAML frontmatter.

Community
Intermediate
xiaoyuge886xiaoyuge886
196

plugin-settings

Standardize plugin configuration storage using YAML frontmatter in local markdown files.

Community
Intermediate
fcakyonfcakyon
1.0k

plugin-settings

Store per-project plugin configuration in .claude/*.local.md files with YAML frontmatter.

Community
Intermediate