skills.rest
lusya123
lusya123COMMUNITY
Explore all skills by this author →
𝕏@ZenoRhoGitHub

Plugin Settings

Store per-project plugin settings in YAML frontmatter within .claude/plugin-name.local.md files.

Updated Jan 13, 2026
Search Tags:#automation#configuration#plugin#settings#claude-code#yaml-frontmatter#local-file
One-click install
npx skills add https://github.com/lusya123/cloudcode --skill plugin-settings-lusya123
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/lusya123/cloudcode/tree/main/claude-code-main/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/lusya123/cloudcode --skill plugin-settings-lusya123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Per-project plugin configuration is scattered across repositories, causing drift and manual overhead; this skill provides a standardized pattern to store per-project settings in a single file with YAML frontmatter and a Markdown body.

Core Features & Use Cases

  • Centralized per-project configuration stored in .claude/plugin-name.local.md with YAML frontmatter for structured settings.
  • Supports enabling/disabling plugins, default values, and lifecycle notes (restart requirement) in the plugin docs.
  • Use cases include per-repo customization, stateful plugin behavior, and per-project prompts or prompts templates stored alongside code.

Quick Start

Create a .claude/plugin-name.local.md file in your project, add YAML frontmatter and a Markdown body, then restart Claude Code to apply changes.

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 in Claude Code?▼

Manage per-project plugin configuration by storing YAML frontmatter in .claude/plugin-name.local.md files. This pattern provides a standardized way to store structured settings and context prompts alongside your repository code.

What is the best way to customize plugin behavior for a specific repository?▼

Customizing plugin behavior for a specific repository is done using a .claude/plugin-name.local.md file. It uses a simple YAML frontmatter schema for settings and a Markdown body to feed activation prompts.

How do I enable or disable plugins and set default values per project?▼

Enable, disable, and set default values for plugins by defining them within the YAML frontmatter of your local configuration file. This structured format centralizes per-repo customization and stateful behavior.

Can I store project-specific prompts and context directly in my codebase?▼

Yes, you can store project-specific prompts and context by adding a Markdown body below the YAML frontmatter in your local configuration file. This feeds prompts directly to the plugin during activation.

Why are my per-project settings not applying after updating the YAML frontmatter?▼

Per-project settings stored in the YAML frontmatter may not apply because Claude Code requires a restart to load the updated configuration. Always restart the application after modifying the local file.

Related Skills

Explore More Software Engineering Skills→
nexus-a1nexus-a1

configuration-init

Initialize project configuration files with an interactive wizard.

Community
Advanced
fcakyonfcakyon
1.0k

plugin-settings

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

Community
Intermediate
PaparusiPaparusi

tong-thong-hien

Identify the current US President using web search.

Community
Basic
softee-psoftee-p

plugin-settings

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

Community
Advanced