skills.rest
LAF-US
LAF-USOFFICIAL
Explore all skills by this author →
GitHub

plugin-settings

Store per-project plugin configuration in YAML frontmatter files.

Updated Dec 17, 2024
Search Tags:#hooks#configuration#plugin#yaml#restart#settings#frontmatter
One-click install
npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill plugin-settings-laf-us
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/LAF-US/IDAHO-VAULT/tree/main/.claude/plugins/marketplaces/claude-plugins-official/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill plugin-settings-laf-us

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 a YAML frontmatter file at .claude/<plugin>.local.md to consolidate enablement, defaults, and state in one discoverable location.

Core Features & Use Cases

  • Per-project configuration via YAML frontmatter in the .claude directory.
  • Deterministic behavior through explicit enable/disable flags, sensible defaults, and documentation for hooks, commands, and agents.
  • Safe, documented update process with guidance on atomic edits and required restarts to apply changes.

Quick Start

Create a file at .claude/my-plugin.local.md with YAML frontmatter to configure the 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 configure per-project plugin behavior in Claude Code?▼

Per-project plugin configuration uses a YAML frontmatter file at .claude/<plugin>.local.md to drive plugin behavior. You create this file with the required fields and restart Claude Code to apply the changes.

What is the YAML frontmatter format for plugin settings?▼

YAML frontmatter stores plugin settings at the top of a local markdown file, defining fields like enabled and mode. This pattern consolidates enablement flags and defaults in one discoverable location for hooks and commands.

Why are my plugin configuration changes not taking effect?▼

Plugin configuration changes require a restart of Claude Code to take effect. You must restart the environment after editing the YAML frontmatter in your .claude local markdown file for the new settings to load.

Can I enable or disable specific hooks per project?▼

Yes, per-project plugin configuration supports explicit enable and disable flags. By setting the enabled field in the YAML frontmatter of your local markdown file, you control whether hooks and commands run for that project.

What is the safest way to update plugin configuration files?▼

The safest update process involves atomic edits to the YAML frontmatter file to prevent partial configuration states. You should validate fields like enabled and mode, then restart Claude Code to apply the changes.

Do I need to manually validate plugin settings in frontmatter?▼

Yes, the configuration pattern requires careful frontmatter parsing and validation of fields like enabled and mode. Ensuring these fields are valid prevents errors when hooks, commands, and reader components execute.

Related Skills

Explore More Software Engineering Skills→
stevessrstevessr

Plugin Settings

Store YAML frontmatter in local .claude files to configure per-project plugin settings.

Community
Advanced
thevibeworksthevibeworks
28

plugin-settings

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

Official
Intermediate
SOLEROMSOLEROM

command-development

Standardize slash-command frontmatter and YAML fields across plugins.

Community
Advanced
Invictusprime7Invictusprime7
1

Plugin Settings

Manage per-project plugin settings via YAML frontmatter in .claude/plugin-name.local.md.

Community
Advanced