skills.rest
ajsai47
ajsai47COMMUNITY
Explore all skills by this author →
WebsiteGitHub

Plugin Settings

Configure Claude Code plugins via .claude/plugin-name.local.md files with YAML frontmatter.

11|2|Updated Mar 31, 2026
Search Tags:#claude-code#yaml-frontmatter#configuration-management#plugin-development#per-project-config#plugin-settings#bash-parsing
One-click install
npx skills add https://github.com/ajsai47/holyclaude --skill plugin-settings-ajsai47
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/ajsai47/holyclaude/tree/main/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/ajsai47/holyclaude --skill plugin-settings-ajsai47

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Claude Code plugins have no built-in mechanism for per-project user configuration, forcing developers to hardcode behavior or require users to edit plugin source code to adjust settings for different projects. This Skill eliminates that friction by providing a standardized, gitignored pattern for storing plugin-specific configuration that persists across sessions.

Core Features & Use Cases

  • Standardized Configuration Pattern: Use .claude/plugin-name.local.md files with YAML frontmatter for structured settings and a markdown body for prompts or additional context.
  • Cross-Component Compatibility: Works seamlessly with plugin hooks, commands, and agents, allowing consistent configuration access across all parts of a plugin.
  • Production-Ready Tooling: Includes parsing scripts, validation logic, atomic update patterns, and real-world examples from popular plugins like multi-agent-swarm and ralph-wiggum.
  • Use Case: A plugin developer can use this Skill to add configurable strict validation mode to their file write hook, allowing users to toggle validation levels per project without modifying hook code.

Quick Start

Ask Claude to create a .claude/your-plugin.local.md configuration file for your current project with validation mode set to strict and the plugin enabled.

Frequently Asked Questions about Plugin Settings

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Claude Code plugins per project without hardcoding values?▼

You can configure Claude Code plugins per project by using standardized .claude/plugin-name.local.md files that combine YAML frontmatter for structured settings with a markdown body for context, preventing the need to hardcode behavior.

How do I store user-specific settings for Claude Code hooks that persist across sessions?▼

To store user-specific settings that persist across sessions, implement gitignored .claude/plugin-name.local.md files using bash parsing patterns and atomic update workflows to safely read and write configuration without requiring git commits.

What is the best way to add a configurable validation toggle to a Claude Code plugin hook?▼

The best way to add a configurable validation toggle is utilizing the cross-component configuration pattern, allowing users to adjust validation levels per project via a local markdown file without modifying the underlying hook code.

Does the per-project configuration pattern work with Claude Code commands and agents?▼

Yes, the per-project configuration pattern works seamlessly with plugin hooks, commands, and agents, providing consistent configuration access across all components of a Claude Code plugin through the standardized local markdown files.

How do I safely parse and update YAML frontmatter in local plugin configuration files?▼

You safely parse and update YAML frontmatter by applying the provided bash parsing patterns, validation logic, and atomic update workflows, which include security guardrails to prevent corruption when reading or writing plugin configuration files.

When do I need a standardized local configuration file for my Claude Code plugin?▼

You need a standardized local configuration file when your plugin requires user-specific settings that vary by project and must persist across sessions without being committed to version control or requiring users to edit plugin source code.

Related Skills

Explore More Software Engineering Skills→
Clay-HHKClay-HHK
2

Plugin Structure

Create and organize Claude Code plugin structures with plugin.json manifests.

Community
Advanced
LeighAtkinsLeighAtkins

Plugin Settings

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

Community
Intermediate
Delqhi-ProjectsDelqhi-Projects
3

Plugin Structure

Scaffold Claude Code plugin structures with manifest configuration and auto-discovery.

Official
Advanced
fcakyonfcakyon
1.0k

plugin-settings

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

Community
Intermediate