skills.rest
nachopalmeri
nachopalmeriCOMMUNITY
Explore all skills by this author →
GitHub

Plugin Settings

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

Updated May 15, 2026
Search Tags:#claude#configuration#plugin#settings#frontmatter#yaml-frontmatter#per-project
One-click install
npx skills add https://github.com/nachopalmeri/agents-system --skill plugin-settings-nachopalmeri
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/nachopalmeri/agents-system/tree/main/.agents/skills/plugin-settings
Command: npx skills add https://github.com/nachopalmeri/agents-system --skill plugin-settings-nachopalmeri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Per-project plugin configuration uses a dedicated .claude/plugin-name.local.md file to store structured settings in YAML frontmatter and a Markdown body for prompts, enabling per-repo customization that stays out of Git when ignored.

Core Features & Use Cases

  • Per-project configuration file: .claude/plugin-name.local.md containing YAML frontmatter and a Markdown body.
  • Frontmatter-driven behavior: enable/disable, specific settings, and references used by hooks, commands, and agents.
  • Safe lifecycle and best practices: defaults, validation, and a GitIgnore-friendly pattern to avoid committing local settings.

Quick Start

Create a file at .claude/my-plugin.local.md with YAML frontmatter describing enabled and other settings, followed by a Markdown body.

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 for Claude?▼

Store per-project Claude plugin configuration in a `.claude/plugin-name.local.md` file using YAML frontmatter for structured settings and a Markdown body for prompts, keeping repo-specific customizations out of Git.

What is YAML frontmatter used for in plugin settings?▼

YAML frontmatter defines structured plugin settings like enabling or disabling features and specifying references, while the Markdown body stores prompts used by hooks, commands, and agents.

How do I prevent local plugin settings from being committed to Git?▼

Local plugin settings stay out of Git by storing them in a `.local.md` file pattern that is GitIgnore-friendly, enforcing per-project ownership while ignoring committed configuration files.

Can Claude hooks and commands read from per-project configuration files?▼

Yes, Claude hooks, commands, and agents read directly from the `.claude/plugin-name.local.md` file, using the YAML frontmatter values to drive their behavior with built-in defaults and validation.

What is the best way to manage per-repo Claude plugin customization?▼

The best way to manage per-repo plugin customization is creating a `.claude/plugin-name.local.md` file with YAML frontmatter for configuration and a Markdown body for prompts, ensuring safe per-project ownership.

Why does my Claude plugin configuration have validation errors?▼

Configuration validation errors occur when the YAML frontmatter in `.claude/plugin-name.local.md` fails the safe lifecycle checks, which enforce defaults and validate settings before hooks or agents execute.

Related Skills

Explore More Software Engineering Skills→
lusya123lusya123

Plugin Settings

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

Community
Intermediate
AVVlasovAVVlasov

plugin-settings

Store and retrieve plugin configuration using YAML frontmatter in markdown files.

Community
Intermediate
eavichayeavichay

git-setup-ignore

Configure .gitignore files to exclude Spec Kit cache and backup artifacts.

Community
Basic
AWS-EducateAWS-Educate

Plugin Settings

Manage per-project AI plugin settings with YAML frontmatter in .claude files.

Official
Intermediate