skills.rest
oguzhanguvenkaya
oguzhanguvenkayaCOMMUNITY
Explore all skills by this author →
GitHub

plugin-settings

Store per-project plugin configuration in YAML frontmatter within a local Markdown file.

Updated May 1, 2026
Search Tags:#claude#configuration#plugin#settings#frontmatter#local.md
One-click install
npx skills add https://github.com/oguzhanguvenkaya/oguzhan_claude_code_configurations --skill plugin-settings-oguzhanguvenkaya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/oguzhanguvenkaya/oguzhan_claude_code_configurations/tree/main/plugins/marketplaces/claude-plugins-official/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/oguzhanguvenkaya/oguzhan_claude_code_configurations --skill plugin-settings-oguzhanguvenkaya

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This pattern enables per-project plugin configuration by storing YAML frontmatter and Markdown content in a local file (.claude/plugin-name.local.md) at the project root, allowing per-project customization without committing user-specific settings.

Core Features & Use Cases

  • Per-project configuration via .claude/plugin-name.local.md
  • YAML frontmatter parsing and Markdown body usage for prompts or context
  • Hooks, commands, and agents can read and apply settings to change plugin behavior
  • Best practices: gitignore, defaults, and safe parsing with atomic updates

Quick Start

Create a file at .claude/plugin-name.local.md with YAML frontmatter and a markdown body to configure the plugin for your project.

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?▼

You can store per-project plugin settings by creating a local file at `.claude/plugin-name.local.md` in your project root, using YAML frontmatter for configuration and a markdown body for context.

What is YAML frontmatter used for in local markdown configuration?▼

YAML frontmatter in local markdown configuration defines structured plugin settings and state, while the markdown body provides prompts or context loaded during plugin activation.

Can I use local markdown files to configure project-specific plugin behavior?▼

Yes, hooks, commands, and agents can read local markdown files to apply project-specific plugin behavior and state without committing user-specific settings to version control.

What is the best way to prevent user-specific plugin settings from being committed?▼

The best way to prevent committing user-specific plugin settings is to add the `.claude/plugin-name.local.md` file to your `.gitignore`, ensuring per-project customization remains local.

What are the limitations of using local markdown files for plugin configuration?▼

Limitations include the necessity of strict YAML frontmatter structure enforcement and the requirement to implement safe parsing with atomic updates to prevent configuration corruption.

Related Skills

Explore More Software Engineering Skills→
andersnygaardandersnygaard
5

rule-making-skill

Analyze a directory and generate .claude/rules/ markdown files for Claude Code.

Community
Intermediate
angrybeaglesangrybeagles

plugin-settings

Parse YAML frontmatter from .claude/plugin-name.local.md files to apply per-project plugin configuration.

Community
Intermediate
AVVlasovAVVlasov

plugin-settings

Store and retrieve plugin configuration using YAML frontmatter in markdown files.

Community
Intermediate
fcakyonfcakyon
1.0k

plugin-settings

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

Community
Intermediate