plugin-settings

Read per-project plugin configuration from `.claude/plugin-name.local.md` files with YAML frontmatter.

28|5|Updated Jun 24, 2025
One-click install
npx skills add https://github.com/thevibeworks/claude-code-docs --skill plugin-settings-thevibeworks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/thevibeworks/claude-code-docs/tree/main/content/github/claude-plugins-official/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/thevibeworks/claude-code-docs --skill plugin-settings-thevibeworks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of making Claude Code plugins behave differently for each repository without repeatedly editing plugin code, by letting you store plugin configuration and state in a per-project file.

Core Features & Use Cases

  • Per-project plugin configuration: Store settings in .claude/plugin-name.local.md so each repo can have its own plugin behavior.
  • YAML frontmatter + instructions: Use YAML frontmatter for structured, machine-readable options and a Markdown body for extra context or prompts.
  • Enabled/disabled plugin state: Control whether a plugin (and related hooks/commands/agents) should run via an enabled flag and other fields like mode or limits.

Quick Start

Create a .claude/my-plugin.local.md file with YAML frontmatter (including enabled: true) and add the plugin-specific settings you want to control for this project.

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 per project without editing plugin code?

Per-project plugin configuration is handled by creating a `.claude/plugin-name.local.md` file with YAML frontmatter, allowing each repository to define its own plugin behavior and state.

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

Local plugin settings use YAML frontmatter between `---` markers for structured machine-readable options, followed by a Markdown body for additional context, prompts, or plugin-specific instructions.

Can I enable or disable plugin hooks and commands for a specific repository?

Yes, you can control whether a plugin and its related hooks, commands, and agents run by setting an `enabled` flag and other fields like mode or limits in the local configuration file.

What happens if the local plugin configuration file is missing?

When the `.claude/plugin-name.local.md` file is missing, the system applies safe defaults to ensure the plugin continues to operate without requiring explicit local configuration.

How do I validate and apply updated plugin settings in Claude Code?

Updated plugin settings require validation and a restart to take effect, ensuring that configuration changes in the local Markdown file are properly loaded and applied to the runtime decisions.

Does consistent file naming matter for per-project plugin state?

Yes, consistent file naming is required for the configuration to be recognized, meaning the file must be named exactly `.claude/plugin-name.local.md` to be parsed correctly.