Plugin Settings

Read YAML frontmatter from .claude/*.local.md files to configure plugins per project.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jasonsie/prompt-dev --skill plugin-settings-jasonsie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/jasonsie/prompt-dev/tree/main/skills/plugin-settings
Command: npx skills add https://github.com/jasonsie/prompt-dev --skill plugin-settings-jasonsie

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Per-project plugin settings pattern solves the problem of per-project configuration and state persistence for Claude Code plugins by providing a standardized, gitignore-friendly location (.claude/*.local.md) for YAML frontmatter based configuration.

Core Features & Use Cases

  • Per-project configuration stored as YAML frontmatter in .claude/my-plugin.local.md
  • Guidance and tooling to read, validate, and apply settings from hooks, commands, and agents
  • Defaults, validation patterns, and security considerations to prevent misconfiguration

Quick Start

Create a .claude/my-plugin.local.md file in your project with YAML frontmatter and a markdown body; Claude Code will load and apply these settings on restart.

Frequently Asked Questions about Plugin Settings

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

FAQPage Schema
How do I store per-project plugin configuration in Claude Code?

You can persist per-project plugin settings by creating a .claude/my-plugin.local.md file with YAML frontmatter and a markdown body, which Claude Code reads and applies automatically.

What is YAML frontmatter parsing for local markdown files?

YAML frontmatter parsing reads structured configuration data from the header of .local.md files, extracting defaults and validation rules to apply across hooks, commands, and agents.

How do I apply gitignore patterns to local plugin settings files?

Local plugin settings files use the .local.md naming convention in the .claude directory, providing a gitignore-friendly location that prevents per-project state from being committed to version control.

Can I use YAML frontmatter settings with hooks and commands?

Yes, YAML frontmatter settings from .local.md files can be read, validated, and applied directly to hooks, commands, and agents to store defaults and persist state across runs.

How do I validate per-project configuration values in Claude Code?

Configuration values are validated using built-in patterns and security considerations that prevent misconfiguration, ensuring safe updates and correct defaults when reading YAML frontmatter from local files.