skills.rest
victorjoshi9
victorjoshi9COMMUNITY
Explore all skills by this author →
GitHub

plugin-settings

Manage per-project plugin settings stored in .claude/*.local.md files.

1|Updated Apr 16, 2026
Search Tags:#claude code#yaml frontmatter#project configuration#markdown parsing#plugin settings#hook automation
One-click install
npx skills add https://github.com/victorjoshi9/content--1- --skill plugin-settings-victorjoshi9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/victorjoshi9/content--1-/tree/main/.claude/plugins/marketplaces/claude-plugins-official/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/victorjoshi9/content--1- --skill plugin-settings-victorjoshi9

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you make Claude Code plugins configurable on a per-project basis by storing plugin state and user preferences in .claude/*.local.md files.

Core Features & Use Cases

  • Project-specific configuration: Keep plugin behavior, flags, and runtime state separate for each repository.
  • YAML frontmatter parsing: Read and validate structured settings from markdown files with predictable fields.
  • Hook and command integration: Use settings files to control hooks, commands, and agents without hardcoding behavior.
  • Safe workflow support: Handle defaults, validation, atomic updates, and gitignored local state for repeatable plugin behavior.

Quick Start

Create a .claude/my-plugin.local.md file with YAML frontmatter and markdown content, then restart Claude Code so your plugin can read the saved settings.

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

Per-project plugin settings are configured by storing state and preferences in .claude/*.local.md files. These files use YAML frontmatter for structured settings and a markdown body, allowing plugins to read project-specific behavior without hardcoding.

How do I parse YAML frontmatter from markdown files for plugin settings?▼

YAML frontmatter parsing extracts structured settings from the top of markdown files. The plugin settings skill validates these predictable fields and separates them from the markdown body content to control hook automation and command behavior.

Can I use local markdown files to control Claude Code hook automation?▼

Yes, .claude/*.local.md files control Claude Code hook automation. Settings stored in these files manage hooks, commands, and agents, enabling configurable behavior without hardcoding values directly into the plugin source.

What is the best way to manage project-specific configuration for Claude plugins?▼

The best way to manage project-specific configuration is using .claude/*.local.md files with YAML frontmatter. This approach supports atomic updates, validation, safe enable/disable handling, and gitignored local state for repeatable plugin behavior across repositories.

Does Claude Code plugin configuration support iteration tracking and runtime state?▼

Yes, Claude Code plugin configuration supports iteration tracking and runtime state. By storing user preferences and plugin state in .claude/*.local.md files, plugins can maintain configurable behavior and track progress per project.

Why are my Claude plugin settings not applying after updating the configuration file?▼

Plugin settings may not apply because Claude Code needs a restart to read updated .claude/*.local.md files. Additionally, validation errors in the YAML frontmatter or unsafe enable/disable handling can prevent atomic updates from taking effect.

Related Skills

Explore More Software Engineering Skills→
hjemmesidekongenhjemmesidekongen
1

plugin-settings

Manage plugin-specific configuration via YAML frontmatter in .claude/plugin-name.local.md files.

Community
Basic
LeighAtkinsLeighAtkins

Plugin Settings

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

Community
Intermediate
fcakyonfcakyon
1.0k

plugin-settings

Store per-project plugin configuration in .claude/*.local.md files with YAML frontmatter.

Community
Intermediate
WizarckWizarck

plugin-settings

Manage per-project plugin settings in Markdown files with YAML frontmatter.

Community
Advanced