plugin-settings

Store and retrieve per-project Claude Code plugin settings via YAML frontmatter.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the need for per-project, user-configurable settings for Claude Code plugins, allowing developers to customize 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 within your project root.
  • YAML Frontmatter: Define structured settings (e.g., enabled: true, mode: strict) using YAML.
  • Markdown Body: Include additional context, prompts, or instructions within the same file.
  • Use Case: A linter plugin can have its strict_mode setting adjusted per project, ensuring different validation levels are applied based on project requirements.

Quick Start

Create a .claude/my-plugin.local.md file with your desired settings and restart Claude Code.

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

Per-project plugin configuration is managed using `.local.md` files with YAML frontmatter and markdown bodies located in the `.claude` directory. This allows you to store and retrieve settings to adapt plugin behavior dynamically across different projects.

What is the best way to customize Claude Code plugin behavior without modifying core code?

Customizing Claude Code plugin behavior without modifying core code is achieved by creating user-managed `.local.md` configuration files. These files use YAML frontmatter for structured settings and a markdown body for additional context.

How do I create per-project settings for a Claude Code plugin?

To create per-project settings, add a `.claude/plugin-name.local.md` file in your project root, define structured settings in the YAML frontmatter, and restart Claude Code to activate the new configuration.

Can I use YAML frontmatter to store strict mode settings for a linter plugin?

Yes, YAML frontmatter can store structured settings like `enabled: true` or `mode: strict` for linter plugins. This ensures different validation levels are applied based on specific project requirements.

How do I prevent sensitive plugin configuration from being committed to git?

Sensitive plugin configuration is protected from git commits by integrating the `.local.md` files into your `.gitignore`. This facilitates user-managed configuration while keeping sensitive project data local.

Why are my Claude Code plugin settings not updating after editing the local markdown file?

Plugin settings updates require a restart-based activation process. If your Claude Code plugin settings are not applying, restart Claude Code to load the new configurations from the `.local.md` file.