Plugin Settings

Standardize per-project plugin settings in YAML frontmatter within .claude files.

432|40|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/tzachbon/smart-ralph --skill plugin-settings-tzachbon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/tzachbon/smart-ralph/tree/main/.agents/skills/Plugin%20Settings
Command: npx skills add https://github.com/tzachbon/smart-ralph --skill plugin-settings-tzachbon

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill enables per-project plugin configuration by documenting a reusable YAML frontmatter pattern that stores plugin settings in a .claude/plugin-name.local.md file. It guides teams on how to manage per-project state, enablement, and prompts via a local settings file.

Core Features & Use Cases

  • Per-project configuration files: .claude/plugin-name.local.md with YAML frontmatter and a markdown body used for prompts or notes.
  • Frontmatter parsing guidance for hooks and commands to read, validate, and apply settings.
  • Templates and examples for creating and reading per-project settings, plus safe, atomic updates to avoid corruption.
  • Use Case: A developer enables a plugin for a single project with specific options while keeping a default configuration in other projects.

Quick Start

To create a settings file for your plugin, generate a .claude/plugin-name.local.md with enabled: true, place your default configuration in the frontmatter, add a short body for prompts, 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 manage per-project plugin configuration in Claude Code?▼

Per-project plugin configuration is managed by creating a .claude/plugin-name.local.md file with YAML frontmatter to store settings, state, and prompts specific to that project.

What is the YAML frontmatter pattern for local plugin settings?▼

The YAML frontmatter pattern stores plugin settings like enablement status and configuration options at the top of a local markdown file, with the body used for prompts or notes.

How do I enable a plugin for a single project without affecting others?▼

To enable a plugin for a single project, generate a .claude/plugin-name.local.md file with enabled: true in the frontmatter, add your configuration, and restart Claude Code to activate the changes.

Can hooks and commands read YAML frontmatter from local settings files?▼

Yes, hooks and commands can parse YAML frontmatter from local settings files to read, validate, and apply per-project plugin configuration safely.

How do I avoid configuration file corruption when updating plugin settings?▼

To avoid corruption, the skill enforces safe frontmatter parsing and atomic updates when writing per-project configuration to the .claude/plugin-name.local.md file.

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

Yes, after modifying the YAML frontmatter in your .claude/plugin-name.local.md file, you must restart Claude Code for the per-project plugin settings to take effect.