plugin-settings

Store and read per-project plugin settings from YAML frontmatter in .claude/plugin-settings.local.md.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/cjrfoto/claude-config --skill plugin-settings-cjrfoto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/cjrfoto/claude-config/tree/main/plugins/marketplaces/claude-plugins-official/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/cjrfoto/claude-config --skill plugin-settings-cjrfoto

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Enable per-project plugin configuration by storing YAML frontmatter in a dedicated local file, so plugin behavior can adapt to each repository without changing global defaults.

Core Features & Use Cases

  • Per-project configuration files named .claude/plugin-settings.local.md stored in the project root
  • YAML frontmatter for structured settings and markdown body for prompts or notes
  • Easy enable/disable via an enabled flag and straightforward reading by hooks and commands

Quick Start

Create or edit .claude/plugin-settings.local.md with a valid YAML frontmatter and restart Claude Code for changes to take effect.

Frequently Asked Questions about plugin-settings

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

FAQPage Schema
How do I configure Claude Code plugins on a per-project basis?

Per-project plugin configuration is managed by storing YAML frontmatter in a dedicated .claude/plugin-settings.local.md file. This allows plugin behavior to adapt to each repository individually without modifying global defaults.

Can I use YAML frontmatter to enable or disable Claude Code plugins locally?

YAML frontmatter supports an enabled flag to easily turn plugins on or off. Hooks and commands can straightforwardly read this structured settings file to control activation per project.

What is the best way to store per-project settings without changing global Claude defaults?

Storing per-project settings in .claude/plugin-settings.local.md isolates configuration to the current repository. This approach ensures global defaults remain untouched while adapting plugin behavior locally.

How does frontmatter parsing work for plugin settings in markdown files?

Frontmatter parsing extracts structured YAML settings from the top of the markdown file, while the body remains available for prompts or notes. The process ensures defaults, validates fields, and documents usage in the plugin README.

Do I need to restart Claude Code after editing local plugin settings?

Restarting Claude Code is required for changes to the local plugin settings file to take effect. Create or edit the YAML frontmatter in .claude/plugin-settings.local.md and restart to apply the new configuration.