skills.rest
AvaTar-ArTs
AvaTar-ArTsCOMMUNITY
Explore all skills by this author →
GitHub

plugin-settings

Configure per-project plugin settings via YAML frontmatter in .claude/*.local.md files.

Updated May 11, 2026
Search Tags:#hooks#claude#plugin#settings#yaml-frontmatter#project-config#local-md
One-click install
npx skills add https://github.com/AvaTar-ArTs/my-supremepowers --skill plugin-settings-avatar-arts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/AvaTar-ArTs/my-supremepowers/tree/main/qwen_skills/plugin-settings
Command: npx skills add https://github.com/AvaTar-ArTs/my-supremepowers --skill plugin-settings-avatar-arts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Per-project plugin configuration is enabled by storing settings in a dedicated YAML frontmatter file under the .claude directory, allowing consistent, project-scoped behavior for Claude Code plugins.

Core Features & Use Cases

  • Per-project configuration files stored at .claude/plugin-name.local.md with YAML frontmatter and Markdown body.
  • Frontmatter parsing to read enabled, mode, and other relevant fields for dynamic behavior.
  • Hooks, commands, and agents can read settings to drive plugin behavior and prompts.
  • Templates, defaults, and best practices to ensure safe, restart-reliable configuration.

Quick Start

Create .claude/my-plugin.local.md with YAML frontmatter and a Markdown body to configure your plugin for the current project.

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

Hooks, commands, and agents can read plugin settings by parsing the YAML frontmatter in .claude/*.local.md files. Fields like enabled and dependencies drive dynamic behavior and prompt routing.

What's the best way to manage project-specific settings for Claude hooks?▼

Using YAML frontmatter in a local Markdown file under the .claude directory is the recommended way to manage project-specific hook settings. This approach provides safe defaults and validation for predictable operation.

Do I need to restart Claude Code after changing YAML frontmatter settings?▼

Yes, you should restart Claude Code after modifying your .claude/*.local.md settings. The skill provides restart guidance to ensure that configuration changes are properly applied and predictable operation is maintained.

Can I use YAML frontmatter to disable a plugin for a specific project?▼

Yes, you can disable a plugin for a specific project by setting the enabled field to false in the YAML frontmatter of the .claude/plugin-name.local.md file. Validation ensures the setting is safely applied.

Why use a local Markdown file instead of a standard YAML config for project configuration?▼

A local Markdown file combines YAML frontmatter for machine-readable settings with a Markdown body for documentation. This approach keeps project-scoped configuration and context together in one predictable, validated format.

Related Skills

Explore More Software Engineering Skills→
GongXLiangGongXLiang

plugin-settings

Manage per-project Claude Code plugin settings via YAML frontmatter files.

Community
Intermediate
jaimedhenriquesjaimedhenriques

command-development

Designs Claude Code slash-command structures and frontmatter for reusable workflows.

Community
Advanced
wellnessbrotherjay-debugwellnessbrotherjay-debug

Plugin Settings

Configure per-project plugin behavior via .claude/*.local.md files with YAML frontmatter.

Community
Intermediate
xlelibertyxleliberty

plugin-settings

Store and retrieve plugin configuration in Markdown files with YAML frontmatter.

Community
Intermediate