skills.rest
zach-source
zach-sourceCOMMUNITY
Explore all skills by this author →
GitHub

Plugin Settings

Manage per-project plugin configuration and state via `.claude/plugin-name.local.md` files.

Updated Feb 18, 2026
Search Tags:#state management#configuration#yaml#plugin development#settings#local files
One-click install
npx skills add https://github.com/zach-source/claude-plugins --skill plugin-settings-zach-source
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/zach-source/claude-plugins/tree/main/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/zach-source/claude-plugins --skill plugin-settings-zach-source

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 configuration and state for Claude Code plugins, allowing for customized behavior without modifying core plugin code.

Core Features & Use Cases

  • Per-Project Configuration: Store settings in .claude/plugin-name.local.md files for project-specific behavior.
  • State Management: Persist agent state or task progress across sessions.
  • Dynamic Behavior: Enable or disable features, set modes, and pass custom parameters to hooks and commands.
  • Use Case: Configure a linter plugin to use strict validation rules only for a specific project, or store the current task ID for a multi-agent system.

Quick Start

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

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 configuration for Claude Code plugins?▼

Per-project configuration for Claude Code plugins is managed using `.claude/plugin-name.local.md` files. These files support YAML frontmatter for structured settings and markdown for context, enabling customized behavior without modifying core plugin code.

How does state management work across sessions for plugin development?▼

State management across sessions works by persisting agent state or task progress within `.claude/plugin-name.local.md` files. This allows plugins to store current task IDs or operational modes locally, ensuring continuity across different sessions.

Do I need bash scripting to parse YAML frontmatter in local plugin files?▼

Yes, bash scripting is required for parsing and file manipulation when using local plugin files. The Skill relies on bash scripts to extract YAML frontmatter and markdown context to dynamically adapt plugin behavior through hooks and commands.

Can I use markdown to pass custom parameters to plugin hooks and commands?▼

Yes, you can pass custom parameters to hooks and commands by writing them in the markdown body of `.claude/plugin-name.local.md` files. This enables dynamic behavior adaptation, allowing features to be enabled or modes set on a per-project basis.

What is the best way to enable strict validation rules for a linter plugin in a specific project?▼

The best way to apply strict validation rules for a specific project is to create a `.claude/plugin-name.local.md` file in the project root. This isolates project-specific configuration from the core plugin, ensuring rules only apply locally.

Related Skills

Explore More Software Engineering Skills→
vrcmsvrcms
1

hookify-rules

Enforce project-specific safety rules via regex pattern matching on commands and files.

Community
Intermediate
DMT123DMT123

plugin-settings

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

Community
Intermediate
deepan-alvedeepan-alve

strategic-compact

Prompt manual context compaction at workflow boundaries via a Claude hook.

Community
Intermediate
ghaerdighaerdi
10

zustand-state

Manage React global state with Zustand and TypeScript middleware.

Community
Intermediate