plugin-settings

Read and interpret per-project plugin configuration from YAML frontmatter in .claude/plugin-settings.local.md files.

231|217|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/fazxes/Claude-code --skill plugin-settings-fazxes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/fazxes/Claude-code/tree/main/stubs/downloads/official-plugins/marketplaces/claude-plugins-official/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/fazxes/Claude-code --skill plugin-settings-fazxes

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Per-project plugin configuration is essential to tailor Claude Code plugins to each repository without committing local state to version control. This skill provides a standardized pattern to store per-project plugin settings in a .claude/plugin-name.local.md file using YAML frontmatter and a Markdown body for contextual instructions.

Core Features & Use Cases

  • Per-project configuration stored at .claude/plugin-name.local.md, enabling repository-specific behavior.
  • YAML frontmatter for structured settings and a Markdown body for prompts, instructions, and prompts to feed back to Claude.
  • Clear templates and examples to read, validate, and apply settings from hooks, commands, and agents, with best practices like gitignore and atomic updates.

Quick Start

Create the file at .claude/plugin-settings.local.md with YAML frontmatter 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 Claude Code plugin behavior for a specific project?

To configure Claude Code plugin behavior per project, create a .claude/plugin-settings.local.md file using YAML frontmatter for structured settings and a Markdown body for contextual instructions, then restart Claude Code to apply changes.

What is the best way to store local plugin settings without committing them to version control?

The best way to store local plugin settings without committing them is using a .claude/plugin-settings.local.md file with YAML frontmatter, combined with gitignore guidance to prevent local state from entering version control.

How does YAML frontmatter work for Claude Code hooks and commands configuration?

YAML frontmatter in local Markdown files provides structured settings for Claude Code hooks and commands, while the Markdown body supplies prompts and instructions that feed back to Claude for per-project behavior tailoring.

Can I use Markdown files to define per-project agent patterns and prompts?

Yes, you can use a Markdown file with YAML frontmatter to define per-project agent patterns and prompts, storing repository-specific instructions and structured settings for Claude Code plugins to read and apply.

How do I validate and safely update plugin configuration files to prevent misconfiguration?

To validate and safely update plugin configuration, use safe parsing practices and atomic file updates provided by the skill's templates and workflows, ensuring reliable application of settings from hooks and commands without misconfiguration.

When do I need a local.md file for Claude Code plugin settings?

You need a local.md file for Claude Code plugin settings when you want to tailor plugin behavior to each repository individually, storing per-project configuration locally without committing that local state to version control.