Plugin Settings

Name: Plugin Settings
Availability: InStock
Author: ss2608-dev

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

Updated Aug 27, 2026

Search Tags:#state management #configuration #yaml #plugin settings #local files #project specific

Ready to run

npx skills add https://github.com/SS2608-dev/Resilience --skill plugin-settings-ss2608-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/SS2608-dev/Resilience/tree/main/.agents/skills/plugin-settings
Command: npx skills add https://github.com/SS2608-dev/Resilience --skill plugin-settings-ss2608-dev

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 pattern for managing per-project plugin configurations and state, allowing for flexible and context-aware plugin behavior without modifying core plugin code or committing sensitive information.

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 key-value settings.
Markdown Body: Include additional context, prompts, or documentation.
Use Case: A linter plugin can have its strict_mode setting adjusted per project by simply creating or editing its .claude/linter.local.md file, without needing to change the plugin's code.

Quick Start

Create a .claude/my-plugin.local.md file in your project root with your desired settings in YAML frontmatter.

Frequently Asked Questions about Plugin Settings

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

FAQPage Schema

How do I manage per-project plugin configurations without modifying core code?▼

You can manage per-project plugin configurations by creating `.claude/plugin-name.local.md` files at your project root, using YAML frontmatter for structured settings and markdown for context without altering core plugin code.

What is the best way to store user-specific plugin state locally?▼

Storing user-specific plugin state locally is best achieved using `.claude/plugin-name.local.md` files with YAML frontmatter, ensuring individual configurations are kept separate and not committed to version control.

How do I read dynamic plugin settings from bash scripts?▼

You can read dynamic plugin settings from bash scripts and commands by storing the desired state in local markdown files, allowing the plugin behavior to adapt based on the parsed YAML frontmatter values.

Can I use YAML frontmatter in local files to adjust linter strict mode per project?▼

Yes, you can adjust a linter's `strict_mode` per project by creating a `.claude/linter.local.md` file with YAML frontmatter, enabling project-specific configuration overrides without changing the plugin itself.

How do I ensure local project configurations are ignored by version control?▼

To ensure local project configurations are ignored by version control, use the `.claude/plugin-name.local.md` file pattern, which is explicitly designed to keep user-specific settings and state uncommitted.

When do I need YAML frontmatter in markdown files for plugin settings?▼

You need YAML frontmatter in markdown files for plugin settings when you want to store structured key-value configurations alongside additional context or documentation for flexible, context-aware plugin behavior.