skills.rest
lucasfth
lucasfthCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

plugin-settings

Automate per-project plugin configuration via YAML frontmatter in .claude/plugin-name.local.md files.

1|Updated Apr 30, 2025
Search Tags:#plugin#yaml#settings#claude-code#frontmatter#local-config
One-click install
npx skills add https://github.com/lucasfth/config --skill plugin-settings-lucasfth
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/lucasfth/config/tree/main/.claude/plugins/marketplaces/claude-plugins-official/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/lucasfth/config --skill plugin-settings-lucasfth

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Plugins can store per-project plugin configuration in the .claude/plugin-name.local.md pattern, enabling configurable Claude Code behavior without committing settings.

Core Features & Use Cases

  • Per-project configuration files: .claude/plugin-name.local.md stores YAML frontmatter and markdown body for prompts or notes
  • Frontmatter-driven configuration: Hooks, commands, and agents read structured fields to control plugin behavior
  • Lifecycle and best practices: Defaults, gitignore guidance, and safe file handling to avoid accidental commits

Quick Start

Create the .claude/plugin-name.local.md file in your project with YAML frontmatter and restart Claude Code to load the settings.

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 on a per-project basis?▼

Per-project plugin configuration is handled by creating a .claude/plugin-name.local.md file with YAML frontmatter, allowing you to define structured settings for hooks, commands, and agents without modifying global configurations.

Can I store plugin settings locally without committing them to my git repository?▼

Yes, local plugin settings stored in the .claude/plugin-name.local.md file can be safely gitignored, preventing accidental commits while still applying configurable behavior to your current project.

What is the best way to apply YAML frontmatter settings to Claude Code hooks and agents?▼

The best way to apply YAML frontmatter settings is placing them in the .claude/plugin-name.local.md file, which standardizes the location for hooks, commands, and agents to read structured fields controlling plugin behavior.

Do I need to restart Claude Code after updating local plugin configuration files?▼

Yes, you need to restart Claude Code after creating or updating the .claude/plugin-name.local.md file to ensure the new YAML frontmatter settings are loaded and applied to the active project.

Why are my per-project YAML settings not being applied to my Claude Code commands?▼

Per-project YAML settings may not apply if the file is not located at the standard .claude/plugin-name.local.md path, or if Claude Code has not been restarted to load the updated frontmatter configuration.

Related Skills

Explore More Software Engineering Skills→
erclxerclx
2

setup-plugins

Automate Claude Code plugin installation and configuration via the claude plugin CLI.

Community
Intermediate
angrybeaglesangrybeagles

plugin-settings

Parse YAML frontmatter from .claude/plugin-name.local.md files to apply per-project plugin configuration.

Community
Intermediate
fcakyonfcakyon
1.0k

plugin-settings

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

Community
Intermediate
Invictusprime7Invictusprime7
1

Plugin Settings

Manage per-project plugin settings via YAML frontmatter in .claude/plugin-name.local.md.

Community
Advanced