plugin-settings

Configure Claude Code plugins per project using .local.md files with YAML frontmatter.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the need for flexible, project-specific configurations for Claude Code plugins, allowing users to tailor plugin behavior without altering global settings or committing sensitive information.

Core Features & Use Cases

  • Per-Project Configuration: Store settings in .claude/plugin-name.local.md files within your project root.
  • YAML Frontmatter: Use structured YAML for settings like enabled, mode, max_retries, etc.
  • Markdown Body: Include additional context, prompts, or documentation within the same file.
  • Use Case: You can disable a plugin for a specific project, set a custom validation level, or provide project-specific instructions that an agent can reference.

Quick Start

Create a new file named .claude/my-plugin.local.md in your project root with your desired settings.

Frequently Asked Questions about plugin-settings

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

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

Per-project plugin configuration in Claude Code is managed using `.local.md` files placed in the `.claude/` directory. These files use YAML frontmatter for structured settings and a markdown body for additional context, enabling project-specific overrides.

Does Claude Code support YAML frontmatter for local plugin settings?

Yes, Claude Code supports YAML frontmatter for local plugin settings. You can define structured variables like `enabled`, `mode`, and `max_retries` in the frontmatter of a `.local.md` file to dynamically adjust plugin behavior per project.

How do I override global plugin settings for a specific project?

To override global plugin settings for a specific project, create a `.claude/plugin-name.local.md` file in your project root. This isolates configuration adjustments without altering global settings or committing sensitive information.

Can I use markdown content alongside YAML frontmatter in Claude Code configuration files?

Yes, you can include markdown content alongside YAML frontmatter in Claude Code configuration files. The markdown body allows you to provide additional context, prompts, or documentation that an agent can reference during execution.

What is the best way to disable a plugin for only one project?

The best way to disable a plugin for a single project is to create a `.local.md` configuration file within that project's `.claude` directory. You can then set the `enabled` variable to false in the YAML frontmatter.

Why use local configuration files instead of global settings for Claude Code plugins?

Local configuration files prevent sensitive project-specific overrides from affecting global settings. Using `.local.md` files ensures that custom validation levels or plugin states remain isolated to the intended project root.