Plugin Settings

Store per-project plugin settings in .claude/*.local.md files with YAML frontmatter.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/arlenagreer/claude_configuration_docs --skill plugin-settings-arlenagreer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/arlenagreer/claude_configuration_docs/tree/main/plugins/marketplaces/claude-code-plugins/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/arlenagreer/claude_configuration_docs --skill plugin-settings-arlenagreer

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill enables plugins to store user-configurable settings and state in local files that are automatically gitignored.

Core Features & Use Cases

  • Per-Project Configuration: Store plugin-specific settings in .claude/plugin-name.local.md files.
  • YAML + Markdown Structure: Use YAML frontmatter for structured configuration and markdown body for prompts and context.
  • Use Case: Imagine you want to temporarily disable a security hook without editing hooks.json. Create a settings file with enabled: false and restart Claude Code.

Quick Start

Create a settings file at .claude/my-plugin.local.md with 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 plugin behavior per-project without editing global settings?

Per-project plugin configuration uses `.claude/plugin-name.local.md` files with YAML frontmatter. Store settings like `enabled: false` or feature flags in frontmatter, restart Claude Code, and the configuration applies only to that project without affecting global hooks.json or other projects.

What's the file structure for plugin settings in Claude Code projects?

Plugin settings use frontmatter-based markdown files stored in `.claude/*.local.md`. YAML frontmatter contains structured configuration fields and validation rules; the markdown body holds prompts and context. Changes take effect after restarting Claude Code.

Can I disable a security hook temporarily without editing hooks.json?

Yes. Create a `.claude/plugin-name.local.md` file with `enabled: false` in YAML frontmatter and restart Claude Code. This disables the hook for the current project only, leaving your global hooks.json unchanged and preserving settings across tasks.

How do local plugin settings handle version control and team collaboration?

Local plugin settings in `.claude/*.local.md` are automatically gitignored, keeping per-project state out of version control. Each team member maintains their own project-specific configuration without conflicts, ideal for enabling strict mode or adjusting file size limits per environment.

What configuration fields can I set in plugin settings files?

Plugin settings support fields like `enabled` for activation, strict mode toggles, file size limits, and feature flags as defined by each plugin. Validate fields against plugin requirements; YAML parsing and extraction ensure atomically-updated configuration that persists across Claude Code sessions.