Plugin Settings

Store per-project plugin settings in YAML frontmatter files.

6|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/pur3v4d3r/pur3-pkb-codebase --skill plugin-settings-pur3v4d3r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/pur3v4d3r/pur3-pkb-codebase/tree/main/.claude/skills/plugin-settings
Command: npx skills add https://github.com/pur3v4d3r/pur3-pkb-codebase --skill plugin-settings-pur3v4d3r

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Centralizes per-project plugin configuration by storing per-project settings in .claude/*local.md files using YAML frontmatter and Markdown bodies, enabling consistent behavior across repos.

Core Features & Use Cases

  • Per-project configuration: stores enabled flags, modes, and other plugin state in a gitignore-friendly local file.
  • Frontmatter parsing: defines structured fields (enabled, mode, etc.) and supports a Markdown body for prompts or context.
  • Hook/Command integration: ready-to-use templates and patterns for reading settings from hooks, commands, and agents.

Quick Start

Create a file at .claude/my-plugin.local.md with YAML frontmatter and a Markdown body to configure the plugin, 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?

You configure per-project plugin settings by creating a YAML frontmatter file at .claude/my-plugin.local.md. This local file stores enabled flags, modes, and persistent state for consistent plugin behavior across repositories.

What is YAML frontmatter used for when managing Claude Code plugins?

YAML frontmatter defines structured fields like enabled flags and modes within local configuration files. It provides a gitignore-friendly way to maintain persistent plugin state and safe defaults across different project environments.

How do I set up local configuration files for Claude Code agents and hooks?

Create a Markdown file with YAML frontmatter in the .claude directory to set up local configuration. This file integrates with hooks, commands, and agents, providing ready-to-use templates to read settings safely.

Do I need to restart Claude Code after modifying YAML frontmatter settings?

Yes, you must restart Claude Code to apply changes after modifying YAML frontmatter settings. The plugin configuration enforces restart semantics to ensure safe defaults and updated state are loaded properly into the environment.

Can I use YAML frontmatter to toggle plugins on and off per repository?

Yes, YAML frontmatter supports enable/disable toggles for plugins on a per-project basis. By storing these flags in a local markdown file, you can control plugin activation independently for each repository environment.

What directories are supported for Claude Code plugin scripts and references?

The plugin configuration supports optional directories for scripts, references, and assets alongside the local frontmatter file. These directories organize workflow automation components and structured guides for hooks and commands.