skills.rest
MinhThang1009
MinhThang1009COMMUNITY
Explore all skills by this author →
GitHub

plugin-settings

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

15|6|Updated May 7, 2026
Search Tags:#hooks#claude#yaml#frontmatter#plugin-settings#local.md
One-click install
npx skills add https://github.com/MinhThang1009/dotclaude --skill plugin-settings-minhthang1009
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/MinhThang1009/dotclaude/tree/main/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/MinhThang1009/dotclaude --skill plugin-settings-minhthang1009

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Per-project plugin configuration is made portable and private by storing YAML frontmatter and a Markdown body in a local file under .claude, allowing per-repo customization that can be ignored by version control.

Core Features & Use Cases

  • Per-project configuration via .claude/plugin-name.local.md for tailored plugin behavior per project.
  • Stable defaults & validation to ensure safe operation when the file is missing or incomplete.
  • Hook/command integration: read, apply, and update settings from project hooks and commands.

Quick Start

Create a per-project plugin config by adding a file at .claude/plugin-name.local.md with YAML frontmatter and a markdown body, then restart Claude Code to load 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?▼

Per-project plugin configuration in Claude Code is managed by creating a local file at .claude/plugin-name.local.md containing YAML frontmatter. This frontmatter drives plugin behavior, enabling per-repo customization that can be ignored by version control.

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

YAML frontmatter in local plugin settings stores fields like enabled and other custom defaults to drive plugin behavior. This mechanism supports enabling, disabling, validation, and per-repo state accessible to hooks, commands, and agents.

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

Yes, you need to restart Claude Code after updating plugin configuration. The skill reads the frontmatter fields and updates the local settings file atomically, but it ensures that applying these changes requires a Claude Code restart to take effect.

Can hooks and commands read and update per-project plugin settings?▼

Hooks and commands can read, apply, and update settings from project files under .claude. This integration allows project hooks and commands to directly access and modify the per-repo state defined in the YAML frontmatter.

What happens if the local plugin configuration file is missing or incomplete?▼

If the local plugin configuration file is missing or incomplete, the system relies on stable defaults and validation to ensure safe operation. These defaults maintain safe plugin behavior even when per-project settings are not fully defined.

Related Skills

Explore More Software Engineering Skills→
MinhThang1009MinhThang1009
15

help

Document Hookify plugin operation and rule configuration for Claude governance.

Community
Intermediate
thevibeworksthevibeworks
28

plugin-settings

Read per-project plugin configuration from `.claude/plugin-name.local.md` files with YAML frontmatter.

Official
Intermediate
LAF-USLAF-US

plugin-settings

Store per-project plugin configuration in YAML frontmatter files.

Official
Intermediate
lusya123lusya123

Plugin Settings

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

Community
Intermediate