Plugin Settings

Store per-project plugin settings in YAML frontmatter within .claude/plugin-name.local.md files.

3|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/Delqhi-Projects/ZOE-Solar-Accounting-OCR --skill plugin-settings-delqhi-projects
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/Delqhi-Projects/ZOE-Solar-Accounting-OCR/tree/main/.claude/PLUGINS/marketplaces/claude-code-plugins/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/Delqhi-Projects/ZOE-Solar-Accounting-OCR --skill plugin-settings-delqhi-projects

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing per-project plugin behavior requires a robust, portable configuration pattern that lives alongside the codebase and is easily ignored by version control.

Core Features & Use Cases

  • Per-project configuration files located at .claude/plugin-name.local.md using YAML frontmatter to store settings and state.
  • Frontmatter-driven hooks and commands read and apply user preferences, enabling consistent plugin behavior across projects.
  • Clear defaults, validation, and guidance for maintaining per-project plugin state, with gitignore and documentation to ensure separation from source.

Quick Start

Create a .claude/plugin-name.local.md in your project with a valid YAML frontmatter block to enable per-project plugin configuration, 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 manage per-project plugin settings in Claude Code?

Per-project plugin settings are managed by storing YAML frontmatter in `.claude/plugin-name.local.md` files, enabling consistent, portable configuration that lives alongside your codebase. This enforces safe defaults and validation for plugin state.

What is the best way to prevent local plugin configuration from being committed to git?

To prevent committing local plugin configuration, store settings in `.claude/plugin-name.local.md` files and add them to gitignore. This enforces safe separation of local configuration from source control while maintaining portability.

How do I configure YAML frontmatter for plugin hooks and commands?

Configure YAML frontmatter for plugin hooks and commands by creating a `.claude/plugin-name.local.md` file with a valid YAML block. Frontmatter-driven hooks read and apply user preferences, enabling consistent plugin behavior across projects.

Does Claude Code plugin development require local configuration files for project patterns?

Claude Code plugin development uses local configuration files to standardize per-project plugin behavior. Storing settings in `.claude/plugin-name.local.md` provides clear defaults, validation, and portable state management across projects.

Why does my per-project plugin state need validation and safe defaults?

Per-project plugin state needs validation and safe defaults to prevent configuration errors and ensure consistent plugin behavior. This approach enforces robust settings management while maintaining separation from source control.

Can I use YAML frontmatter to store local config for multiple plugins in one project?

Yes, YAML frontmatter can store local config for multiple plugins by creating separate `.claude/plugin-name.local.md` files for each plugin. This standardizes per-project configuration with clear defaults and validation.