plugin-settings

Creates .claude/pslugin-settings.local.md files with frontmatter configuration for Claude Code plugins.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Per-project plugin configuration is scattered across codebases and hooks. This skill standardizes storage by using a dedicated local file (.claude/plugin-settings.local.md) that combines YAML frontmatter with a Markdown body for prompts and notes, enabling per-repo configuration and easier governance.

Core Features & Use Cases

  • Centralized per-project configuration via .claude/plugin-settings.local.md, enabling consistent plugin behavior across a repository.
  • Frontmatter-based configuration fields (enabled, strict_mode, max_retries, etc.) plus a Markdown body for prompts, notes, and contextual guidance.
  • Clear guidance for reading, updating, and ignoring local settings (gitignore patterns, atomic writes, default fallbacks).

Quick Start

Create the .claude/plugin-settings.local.md in your project and define initial settings.

Frequently Asked Questions about plugin-settings

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I store per-project plugin settings for Claude Code?

Store per-project plugin settings by creating a .claude/plugin-settings.local.md file using YAML frontmatter for configuration fields like enabled and strict_mode, plus a Markdown body for prompts and notes.

What is the best way to manage Claude Code plugin configuration across multiple repositories?

Managing Claude Code plugin configuration across repositories is best handled by standardizing storage in a dedicated local file with YAML frontmatter, enabling consistent per-repo plugin behavior and easier governance.

Can I use YAML frontmatter to control plugin activation and mode selection during CI?

Yes, you can use YAML frontmatter in the local settings file to control per-project activation, mode selection, and state management during development, testing, and CI.

How do I safely update local plugin settings without breaking existing configuration?

Safely update local plugin settings by following guidance for atomic writes, default fallbacks, and gitignore patterns to prevent committing local configuration and ensure safe updates.

What configuration fields are supported in the plugin-settings frontmatter schema?

The frontmatter schema supports configuration fields including enabled, strict_mode, and max_file_size, allowing granular control over plugin behavior within a repository.