skills.rest
mobster570
mobster570COMMUNITY
Explore all skills by this author →
GitHub

plugin-settings

Manage per-project plugin configuration with YAML frontmatter in .claude/plugin-name.local.md files.

Updated Mar 28, 2026
Search Tags:#hooks#plugin#yaml#settings#claude-code#frontmatter#local-md
One-click install
npx skills add https://github.com/mobster570/oc-claude-plugin-dev --skill plugin-settings-mobster570
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/mobster570/oc-claude-plugin-dev/tree/main/plugin-src/skills/plugin-settings
Command: npx skills add https://github.com/mobster570/oc-claude-plugin-dev --skill plugin-settings-mobster570

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Per-project plugin configuration is error-prone when scattered across files and environments. This skill provides a standardized pattern to store per-project settings in .claude/plugin-name.local.md using YAML frontmatter and a markdown body that can be read by hooks, commands, and agents.

Core Features & Use Cases

  • Per-project configuration files in the .claude/ pattern to isolate settings for a specific plugin.
  • YAML frontmatter for structured fields (enabled, mode, etc.) and a markdown body for prompts or contextual notes.
  • Hooks, commands, and agents can read settings with sensible defaults and consistent validation.

Quick Start

Create or edit a file at .claude/plugin-name.local.md with YAML frontmatter to configure the plugin for the current project.

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 in Claude Code?▼

Per-project plugin settings are configured by creating a file at .claude/plugin-name.local.md with YAML frontmatter for structured fields and a markdown body for prompts. This isolates plugin configuration for the current project.

What is the .claude local.md frontmatter pattern for plugin configuration?▼

The .claude local.md frontmatter pattern stores YAML-based structured settings and a markdown body in a single file. This allows hooks, commands, and agents to safely parse per-project plugin configurations with consistent defaults and validation.

Can Claude Code hooks and agents read YAML frontmatter settings?▼

Yes, hooks, commands, and agents can read YAML frontmatter settings from the .claude/plugin-name.local.md file. The pattern enforces safe parsing, sensible defaults, and validation across all Claude Code workflow components.

What's the best way to manage YAML settings across multiple Claude Code projects?▼

The best way to manage YAML settings across multiple Claude Code projects is the .claude/plugin-name.local.md pattern. It isolates per-project configurations to prevent errors from scattered files and environments while enforcing safe parsing and validation.

Why does per-project plugin configuration fail when scattered across files?▼

Per-project plugin configuration fails when scattered because it lacks standardized parsing and validation. The .claude local.md frontmatter pattern solves this by centralizing YAML settings and markdown bodies for safe, consistent access by hooks and agents.

Related Skills

Explore More Software Engineering Skills→
Hex-4Hex-4

plugin-settings

Manages Claude Code plugin settings via YAML frontmatter in .local.md files.

Community
Advanced
fcakyonfcakyon
1.0k

plugin-settings

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

Community
Intermediate
gkganesh12gkganesh12
1

gk-architect

Generate an ARCHITECTURE.md defining structural patterns and technical constraints for software projects.

Community
Advanced
wellnessbrotherjay-debugwellnessbrotherjay-debug

Plugin Settings

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

Community
Intermediate