skills.rest
murphyjoseph
murphyjosephCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Plugin Settings

Store per-project plugin settings in YAML frontmatter files under .claude with .local.md suffix.

Updated Mar 1, 2026
Search Tags:#configuration#plugin#yaml#settings#claude-code#frontmatter#local-md
One-click install
npx skills add https://github.com/murphyjoseph/dojo-kit --skill plugin-settings-murphyjoseph
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/murphyjoseph/dojo-kit/tree/main/.agents/skills/plugin-settings
Command: npx skills add https://github.com/murphyjoseph/dojo-kit --skill plugin-settings-murphyjoseph

SYSTEM DOCUMENTATION & REQUIREMENTS

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

## What problem does it solve? This skill enables per-project plugin configuration by storing YAML frontmatter in a dedicated local markdown file, allowing teams to customize plugin behavior without embedding sensitive data in code or hard-wiring defaults.

## Core Features & Use Cases

  • Per-project configuration stored in .claude/plugin-name.local.md with a YAML frontmatter and Markdown body.
  • Hooks and commands read settings to enable/disable plugins, select modes, apply defaults, and persist state across a project.
  • Templates, examples, and best practices guide users on creating, validating, and safely ignoring local settings.

### Quick Start Create the file .claude/my-plugin.local.md with YAML frontmatter and a Markdown body, then restart Claude Code to apply changes.

Frequently Asked Questions about Plugin Settings

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

FAQPage Schema
How do I configure per-project plugin settings in Claude Code?▼

Store per-project plugin configuration by creating a YAML frontmatter file under the .claude directory with a .local.md suffix. This local markdown file allows teams to customize plugin behavior without hard-wiring defaults.

What is the best way to manage plugin configuration without embedding settings in code?▼

Using a YAML frontmatter file in a local markdown document is the best way to manage plugin configuration without hard-wiring defaults. It separates customizable behavior from code, using the Markdown body to carry prompts or notes.

How do I apply changes to YAML frontmatter settings for Claude Code plugins?▼

To apply changes to YAML frontmatter settings for Claude Code plugins, you must restart Claude Code. Hooks read the updated configuration from the .local.md file upon restart to ensure changes take effect.

Does Claude Code support local markdown files for storing plugin state?▼

Yes, Claude Code supports local markdown files for storing plugin state. Placing a file with a .local.md suffix in the .claude directory allows you to persist state and apply defaults across a project.

Why do my updated plugin settings in the YAML frontmatter not take effect?▼

Updated plugin settings in the YAML frontmatter may not take effect because Claude Code requires a restart to apply changes. The configuration is read via hooks at startup, so the application must be restarted to load new settings.

Related Skills

Explore More Software Engineering Skills→
phillip-hirschphillip-hirsch

plugin-settings

Manage user-configurable settings for Claude Code plugins using YAML frontmatter.

Community
Intermediate
fcakyonfcakyon
1.0k

plugin-settings

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

Community
Intermediate
SigmacodeatSigmacodeat

skill-optimizer

Optimize AI skill instructions through benchmark-driven validation cycles.

Community
Advanced
lobehublobehub
81.4k

add-setting-env

Implement server-side environment variables for default user settings.

Official
Advanced