skills.rest
daithang59
daithang59COMMUNITY
Explore all skills by this author →
GitHub

Plugin Settings

Manage per-project plugin settings via `.claude/plugin-name.local.md` files with YAML frontmatter.

1|Updated Mar 13, 2026
Search Tags:#state management#configuration#yaml#local config#plugin settings#project specific
One-click install
npx skills add https://github.com/daithang59/docvault --skill plugin-settings-daithang59
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/daithang59/docvault/tree/main/.agent/skills/configured-agent
Command: npx skills add https://github.com/daithang59/docvault --skill plugin-settings-daithang59

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a standardized way to manage per-project plugin configurations and state, allowing plugins to adapt their behavior based on the specific project context without requiring code changes or global settings.

Core Features & Use Cases

  • Per-Project Configuration: Store settings in .claude/plugin-name.local.md files at the project root.
  • YAML Frontmatter: Use YAML for structured settings (e.g., enabled: true, mode: strict).
  • Markdown Body: Include additional context, prompts, or documentation within the same file.
  • Use Case: A linter plugin can use a .claude/linter.local.md file to enable/disable specific rules or set severity levels for a particular project, overriding its global defaults.

Quick Start

Create a .claude/my-plugin.local.md file with enabled: true and mode: standard in your project root.

Frequently Asked Questions about Plugin Settings

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage plugin configuration on a per-project basis?▼

Per-project plugin configuration is managed using `.claude/plugin-name.local.md` files at the project root. These files store project-specific settings separately from global defaults, allowing plugins to adapt their behavior dynamically.

What is the best way to override global plugin settings for a specific project?▼

Overriding global plugin settings is best handled by creating a `.claude/plugin-name.local.md` file. This approach keeps user-managed settings version-control-agnostic while enabling project-specific behavior modifications without code changes.

Can I use YAML frontmatter for structured plugin settings?▼

YAML frontmatter is fully supported for structured plugin settings within `.local.md` files. You can define key-value pairs like `enabled: true` or `mode: strict` to control plugin state and configuration precisely.

How do I include additional context or prompts in my local plugin configuration file?▼

Additional context, prompts, or documentation can be included directly in the markdown body of the `.claude/plugin-name.local.md` file. This sits alongside the YAML frontmatter, combining structured settings with free-form text.

Does per-project plugin state management work without modifying the plugin's source code?▼

Per-project state management works entirely without modifying source code. Plugins read the `.claude/plugin-name.local.md` configuration files to adapt their behavior based on the specific project context, requiring no code adjustments.

When should I not use markdown files for local config and state management?▼

You should avoid using markdown local config files if your project requires strict schema validation or complex nested data structures beyond YAML frontmatter capabilities. The format prioritizes flexible, human-readable settings over deeply structured database-like state.

Related Skills

Explore More Software Engineering Skills→
ffalorffalor
1

plugin-settings

Store and retrieve per-project plugin configuration using YAML frontmatter in markdown files.

Community
Intermediate
FacuMFacuM

plugin-settings

Manage per-project plugin configurations using .local.md files with YAML frontmatter.

Community
Intermediate
CaptainCrouton89CaptainCrouton89
25

Writing Hookify Rules

Create Hookify rules with YAML frontmatter to monitor events and surface contextual messages.

Community
Basic
BekaChkhiroBekaChkhiro
1

planSettingsReset

Reset Claude Plan Plugin settings to defaults for local or global scopes.

Community
Advanced