skills.rest
softee-p
softee-pCOMMUNITY
Explore all skills by this author →
𝕏@mkw3ddGitHub

plugin-settings

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

Updated Jan 24, 2026
Search Tags:#configuration#plugin#yaml#settings#claude-code#frontmatter
One-click install
npx skills add https://github.com/softee-p/redwoodSDK-toolkit --skill plugin-settings-softee-p
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/softee-p/redwoodSDK-toolkit/tree/main/dev-plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/softee-p/redwoodSDK-toolkit --skill plugin-settings-softee-p

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Plugins often need per-project configuration that travels with the repository and is not hard-coded. This Skill defines a standard pattern to store per-project plugin settings and state in .claude/{plugin-name}.local.md files using YAML frontmatter and a Markdown body, enabling consistent discovery, sharing, and reloading of configuration within Claude Code plugins.

Core Features & Use Cases

  • Per-project configuration files at .claude/{plugin-name}.local.md that store an enabled flag and settings in YAML frontmatter.
  • A Markdown body for prompts, notes, and runtime context that can be loaded into the plugin at activation.
  • Guidelines for reading/writing settings from hooks, commands, and agents, with defaults, restart requirements, and gitignore recommendations.
  • Clear templates and examples for creating, updating, and validating settings files to maintain consistency across projects.

Quick Start

Create .claude/plugin-name.local.md with YAML frontmatter and a Markdown body to configure your plugin, then restart Claude Code for changes to take effect.

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

Per-project plugin configuration is stored in .claude/{plugin-name}.local.md files using YAML frontmatter for settings and a Markdown body for runtime context. This pattern ensures configuration travels with the repository instead of being hard-coded.

What is the best way to read and write plugin settings from Claude Code hooks?▼

Plugin settings are read and written from hooks, commands, and agents by parsing the YAML frontmatter in .claude files. This Skill provides standard templates for creating, updating, and validating these settings files to maintain consistency.

Do I need to restart Claude Code after updating plugin YAML frontmatter settings?▼

Yes, Claude Code requires a restart for frontmatter settings changes to take effect. This Skill enforces a safe, restart-required pattern with documented file locations, defaults, and read/write templates to prevent runtime conflicts.

Can I use YAML frontmatter in .claude files to manage plugin state and defaults?▼

YAML frontmatter in .claude files manages an enabled flag, plugin settings, and defaults. The Markdown body stores prompts, notes, and runtime context that can be loaded into the plugin at activation, sharing state across hooks.

Should I gitignore the .claude local settings files generated for plugin configuration?▼

The Skill provides gitignore recommendations for .claude/{plugin-name}.local.md files. Because these files store per-project configuration and runtime state, you should follow the documented guidelines to decide whether to track or ignore them.

Why does my Claude Code plugin configuration not persist across repository clones?▼

Plugin configuration fails to persist when hard-coded instead of stored in repository files. Defining settings in .claude/{plugin-name}.local.md with YAML frontmatter ensures consistent discovery, sharing, and reloading of configuration across cloned repositories.

Related Skills

Explore More Software Engineering Skills→
phucle297phucle297

plugin-settings

Parse YAML frontmatter from .claude/plugin-name.local.md configuration files.

Community
Intermediate
angrybeaglesangrybeagles

plugin-settings

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

Community
Intermediate
thevibeworksthevibeworks
28

plugin-settings

Read per-project plugin configuration from `.claude/plugin-name.local.md` files with YAML frontmatter.

Official
Intermediate
fcakyonfcakyon
1.0k

plugin-settings

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

Community
Intermediate