plugin-settings

Store and retrieve Claude Code plugin settings in .claude/*.local.md files with YAML frontmatter and markdown body.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/julianobarbosa/.claude --skill plugin-settings-julianobarbosa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/julianobarbosa/.claude/tree/main/plugins/marketplaces/claude-plugins-official/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/julianobarbosa/.claude --skill plugin-settings-julianobarbosa

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill solves the problem of making Claude Code plugins configurable per project without editing plugin code, by standardizing how users store plugin state and settings in a predictable .claude/plugin-name.local.md file.

Core Features & Use Cases

  • Per-project plugin configuration: Store plugin enabled/disabled flags and configuration fields inside .claude/plugin-name.local.md in the project root.
  • Structured YAML frontmatter + markdown body: Use YAML frontmatter for machine-readable settings and the markdown body for prompts, notes, or additional instructions.
  • Hook/command/agent friendly: Read settings files from bash hooks and commands, and allow agents to adapt behavior based on parsed configuration.
  • Lifecycle management: Supports user-managed state (typically kept out of git) using the .local.md pattern plus validation guidance.

Quick Start

Create a .claude/plugin-settings.local.md file in your project with YAML frontmatter (including enabled: true) and a short markdown body describing any extra behavior you want the plugin to follow.

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 per project without editing plugin code?

You can configure Claude Code plugins per project by creating a `.claude/plugin-name.local.md` file with YAML frontmatter for settings and a markdown body for instructions, preventing the need to edit plugin code directly.

What's the best way to store per-project plugin state in Claude Code?

Storing per-project plugin state is best handled through `.claude/plugin-name.local.md` files using YAML frontmatter for machine-readable settings and markdown for user prompts, keeping state localized and predictable.

How does YAML frontmatter manage plugin enabled flags and operational modes?

YAML frontmatter manages plugin behavior by storing structured fields like `enabled: true` and operational mode flags inside the local markdown file, which bash hooks and agents parse to adapt behavior.

Can I read Claude Code plugin settings from bash hooks and commands?

Yes, bash hooks and commands can read plugin settings files by parsing the YAML frontmatter from the `.claude/plugin-name.local.md` file, allowing scripts to adjust execution based on the parsed configuration.

Do I need to gitignore local plugin configuration files in my project?

Yes, you should add `.claude/plugin-name.local.md` files to gitignore to prevent accidental commits, as the `.local.md` pattern is designed for user-managed state kept locally rather than shared across the team.

What happens if a Claude Code plugin settings file is missing?

When a plugin settings file is missing, the system applies safe defaults to maintain functionality, ensuring hooks, commands, and agents continue operating reliably without requiring explicit configuration files.