plugin-settings

Store per-project plugin configuration in a local YAML frontmatter and Markdown file.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The plugin settings pattern provides a per-project configuration store using the .claude/plugin-name.local.md file, combining YAML frontmatter for structured options with a Markdown body for contextual prompts and notes.

Core Features & Use Cases

  • File location and structure: place a YAML-frontmatter file at project root under .claude/plugin-name.local.md to store config and state.
  • Structured configuration: use YAML frontmatter for configuration fields (enabled, setting1, numeric_setting, list_setting) and a Markdown body for prompts or context.
  • Lifecycle and usage: read by Hooks, Commands, and Agents to tailor behavior per project; files are intended to be kept out of Git via .gitignore.

Quick Start

Create a file at .claude/plugin-name.local.md with YAML frontmatter and Markdown body to configure this plugin per project.

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 without modifying the codebase?

Per-project plugin configuration can be stored in a dedicated local file using YAML frontmatter for structured settings and a Markdown body for context, keeping plugin behavior tunable without altering the codebase.

What is the file structure for local plugin settings in Claude Code?

The local plugin settings file uses YAML frontmatter containing enabled, settings, numeric, and list fields, paired with a Markdown body for contextual prompts, read by hooks, commands, and agents at runtime.

How do I create a local configuration file for Claude Code hooks and agents?

Create a file at .claude/plugin-name.local.md in your project root, adding YAML frontmatter for configuration fields and a Markdown body for notes to configure the plugin per project.

Does plugin configuration via YAML frontmatter work with Git repositories?

Yes, the local configuration files are designed to be kept out of Git via .gitignore, ensuring per-project settings remain local and do not alter the shared codebase.

Can I use Markdown body content to provide context for Claude Code agents?

Yes, the Markdown body in the .claude/plugin-name.local.md file stores contextual prompts and notes that are read by hooks, commands, and agents to tailor behavior per project.

What is the best way to keep plugin behavior tunable across different projects?

Using a dedicated local file with YAML frontmatter per project allows you to maintain separate configurations, keeping plugin behavior tunable across different projects without altering the codebase.