Plugin Settings

Store YAML frontmatter in local .claude files to configure per-project plugin settings.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/stevessr/dotsfiles --skill plugin-settings-stevessr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/stevessr/dotsfiles/tree/main/dot_claude/private_plugins/private_marketplaces/claude-code-plugins/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/stevessr/dotsfiles --skill plugin-settings-stevessr

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 storing YAML frontmatter in project-local .claude files, providing a standardized pattern to customize and persist plugin behavior without committing secrets.

Core Features & Use Cases

  • Per-project configuration files: .claude/plugin-name.local.md to enable, disable, and tune plugin behavior.
  • YAML frontmatter + markdown body: structured settings with a descriptive prompt or notes.
  • Safe defaults and restart requirements: changes apply after Claude Code is restarted and are gitignored to protect privacy.
  • Reusable templates: ready-made templates to guide configuration in various projects.

Quick Start

Create a file at .claude/plugin-name.local.md with YAML frontmatter and a markdown body to configure the plugin, 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 configure per-project plugin behavior in Claude Code?▼

You configure per-project plugin behavior by creating a `.claude/plugin-name.local.md` file containing YAML frontmatter and markdown body, then restarting Claude Code to apply the local settings.

What is YAML frontmatter used for in local plugin settings?▼

YAML frontmatter stores structured per-project plugin settings such as enablement, mode selection, and defaults in local `.claude` files, separating configuration from the descriptive markdown body.

Does per-project plugin configuration require restarting Claude Code?▼

Yes, per-project plugin configuration requires restarting Claude Code. Changes to local `.claude` files and YAML frontmatter are only parsed and applied after a session restart.

Are local plugin configuration files committed to the repository?▼

No, local `.claude` plugin configuration files are gitignored to protect privacy and prevent committing secrets, ensuring per-project settings remain isolated to the local environment.

Can I set default modes and enablement for plugins in individual projects?▼

Yes, you can enable, disable, and tune plugin behavior for individual projects by defining mode selection and defaults within the YAML frontmatter of local `.claude` files.

Why are my local plugin settings not working after editing the YAML file?▼

Local plugin settings fail to apply if Claude Code is not restarted after editing the YAML frontmatter, as the restart requirement triggers frontmatter parsing, validation, and state application.