Plugin Settings

Store per-project plugin configuration in YAML frontmatter within .claude files.

1|Updated Jan 27, 2026

Search Tags:#claude #plugin #yaml #settings #frontmatter #local-config

Ready to run

npx skills add https://github.com/kurohit2/MlProject --skill plugin-settings-kurohit2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/kurohit2/MlProject/tree/main/.agents/skills/plugin-settings
Command: npx skills add https://github.com/kurohit2/MlProject --skill plugin-settings-kurohit2

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The Plugin Settings pattern enables per-project configuration for Claude Code plugins by storing YAML frontmatter and a markdown body in a dedicated .claude file, keeping project-specific behavior isolated and git-ignored.

Core Features & Use Cases

Per-project configuration stored in .claude/plugin-name.local.md with YAML frontmatter and a markdown body
Read and apply settings from hooks, commands, and agents
Manage plugin state (enabled, mode, dependencies) per project to tailor behavior
Use cases include enabling/disabling features, switching validation modes, and documenting prompts or context

Quick Start

Create or update the file .claude/plugin-name.local.md with YAML frontmatter and a markdown body to configure the plugin for the current project.

Frequently Asked Questions about Plugin Settings

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

FAQPage Schema

How do I store per-project plugin configuration in Claude Code?▼

You store per-project plugin configuration by writing YAML frontmatter and a markdown body into the .claude/plugin-name.local.md file. This file keeps project-specific behavior isolated and git-ignored.

What is the best way to manage Claude plugin state across different projects?▼

Manage Claude plugin state by storing settings like enabled status, mode, and dependencies in YAML frontmatter. This approach allows you to tailor and enforce plugin behavior for each project.

Can I apply YAML settings from hooks, commands, and agents in Claude?▼

Yes, you can read and apply YAML settings from the local configuration file across hooks, commands, and agents. This enforces per-project plugin behavior and enables dynamic configuration.

How do I configure a Claude plugin using YAML frontmatter?▼

To configure a plugin, create or update the .claude/plugin-name.local.md file with YAML frontmatter and a markdown body. This defines project-specific settings, state, and context for the plugin.

Do I need to gitignore local Claude plugin settings files?▼

Yes, you need to gitignore local Claude plugin settings files. The .claude/plugin-name.local.md file is designed to keep project-specific configuration isolated and should follow gitignore practice.

What are the limitations of using local markdown files for plugin settings?▼

Limitations include the need for safe parsing and validation of YAML fields. You must also adhere to gitignore practice and provide clear user documentation within the markdown body.