Plugin Settings

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

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/AWS-Educate/template-nextjs-sanity-tailwind-amplify --skill plugin-settings-aws-educate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/AWS-Educate/template-nextjs-sanity-tailwind-amplify/tree/main/.agents/skills/plugin-settings
Command: npx skills add https://github.com/AWS-Educate/template-nextjs-sanity-tailwind-amplify --skill plugin-settings-aws-educate

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a standardized pattern for managing per-project configurations and state for AI code plugins, ensuring consistent behavior across different development environments without cluttering version control.

Core Features & Use Cases

  • Per-Project Configuration: Store settings in .claude/plugin-name.local.md files.
  • YAML Frontmatter: Define structured settings (e.g., enabled: true, mode: strict).
  • Markdown Body: Include additional context, prompts, or documentation.
  • Bash Script Integration: Easily parse settings within hooks and scripts.
  • Use Case: A code formatting plugin can have its strict_mode setting adjusted per project by creating a .claude/formatter.local.md file, without needing to commit this change.

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 without version control conflicts?▼

Per-project plugin configuration avoids version control conflicts by storing settings in local `.claude/plugin-name.local.md` files. This enables environment-specific plugin behavior and state persistence without committing changes to the repository.

What is the best way to parse YAML frontmatter settings within bash scripts?▼

Parsing YAML frontmatter within bash scripts is supported by robust bash parsing utilities provided for hooks and commands. These utilities extract structured settings like `enabled: true` or `mode: strict` directly from the local configuration files.

Can I use markdown files to define environment-specific settings for AI code plugins?▼

Markdown files can define environment-specific settings for AI code plugins by utilizing YAML frontmatter for structured settings and the markdown body for additional context, prompts, or documentation.

How do I set up local config state for a code formatting plugin across different environments?▼

Local config state for a code formatting plugin is set up by creating a `.claude/formatter.local.md` file with desired settings. Adjusting settings like `strict_mode` per project requires creating this file and restarting Claude Code.

Does storing plugin settings in local markdown files prevent committing local state to git?▼

Storing plugin settings in local markdown files prevents committing local state to git by using the `.local.md` naming convention. This pattern keeps environment-specific plugin behavior separate from version control.

Why do I need environment-specific plugin behavior for AI code plugins?▼

Environment-specific plugin behavior is needed to ensure consistent plugin execution across different development environments. Standardized local configuration files provide the necessary state persistence and settings without cluttering version control.