Plugin Settings

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

Updated Apr 8, 2026

Search Tags:#automation #configuration #plugin #yaml #metadata #local #settings

Ready to run

npx skills add https://github.com/wellnessbrotherjay-debug/ts-residence --skill plugin-settings-wellnessbrotherjay-debug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/wellnessbrotherjay-debug/ts-residence/tree/main/.agents/skills/plugin-settings
Command: npx skills add https://github.com/wellnessbrotherjay-debug/ts-residence --skill plugin-settings-wellnessbrotherjay-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Managing plugin behavior across projects can be cumbersome, requiring manual edits to hidden configuration files and inconsistent handling of YAML frontmatter.

Core Features & Use Cases

Standardized Settings Files: Uses .claude/*.local.md with YAML frontmatter for clear, version-controlled configuration.
Parsing Utilities: Bash scripts to read, validate, and apply settings for hooks, commands, and agents.
Use Cases: Enable or disable plugins, adjust validation modes, set feature flags, or store task-specific state without modifying code.

Quick Start

Ask the assistant to create or update a .claude/my-plugin.local.md file with your desired configuration.

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 settings without modifying code?▼

Per-project plugin settings are configured by storing configuration in .claude/*.local.md files with YAML frontmatter. This approach applies settings to hooks, commands, and agents without requiring code modifications.

What is the best way to manage YAML frontmatter for local plugin configuration?▼

YAML frontmatter for local plugin configuration is managed using standardized .claude/*.local.md files. Parsing utilities read, validate, and apply these settings to define plugin behavior across projects.

How do I enable or disable plugins and set feature flags per project?▼

Plugins and feature flags are enabled or disabled by creating or updating a .claude/my-plugin.local.md file with your desired configuration. This stores task-specific state and adjusts validation modes.

Does this approach work with version control systems for storing configuration state?▼

Yes, this approach uses .claude/*.local.md files which provide clear, version-controlled configuration. Storing settings in these standardized files ensures consistent handling across your project repository.

Why does my plugin configuration require manual edits to hidden files?▼

Plugin configuration requires manual edits to hidden files when lacking a standardized settings format. Using .claude/*.local.md files with YAML frontmatter eliminates this cumbersome process by providing parsing utilities.