skills.rest
Claude-Code-Community-Ireland
Claude-Code-Community-IrelandOFFICIAL
Explore all skills by this author →
GitHub

Plugin Settings

Configure Claude Code plugins per project using `.claude/plugin-name.local.md` files with YAML frontmatter.

10|5|Updated Jan 29, 2026
Search Tags:#configuration#plugin management#yaml frontmatter#local config#plugin settings#project specific
One-click install
npx skills add https://github.com/Claude-Code-Community-Ireland/claude-code-resources --skill plugin-settings-claude-code-community-ireland
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/Claude-Code-Community-Ireland/claude-code-resources/tree/main/plugins/vibeworks-library/skills/plugin-settings
Command: npx skills add https://github.com/Claude-Code-Community-Ireland/claude-code-resources --skill plugin-settings-claude-code-community-ireland

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the need for project-specific plugin configurations, allowing users to customize plugin behavior without altering global settings or committing sensitive information.

Core Features & Use Cases

  • Per-Project Configuration: Store settings in .claude/plugin-name.local.md files for granular control.
  • YAML Frontmatter: Use structured data for settings like enabled, mode, max_retries.
  • Markdown Body: Include additional context, prompts, or documentation within the settings file.
  • Use Case: A developer can disable a linter plugin for a specific project where its rules are too strict, or configure a data processing plugin with project-specific paths and parameters.

Quick Start

Create a .claude/my-plugin.local.md file in your project root to configure plugin settings.

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 for a specific project?▼

Per-project configuration uses `.claude/plugin-name.local.md` files to store granular, project-specific plugin settings, allowing you to customize behavior locally without altering global configurations.

Can I use YAML frontmatter to manage local plugin settings?▼

Yes, YAML frontmatter enables structured local plugin settings like `enabled`, `mode`, and `max_retries`, while the markdown body provides additional context or documentation within the same configuration file.

What is the best way to disable a linter plugin for just one project?▼

Using a `.claude` local configuration file with YAML frontmatter is the best way to disable a linter for a single project, setting the `enabled` parameter to false to override default behavior.

Does plugin configuration support adding custom context and prompts?▼

Yes, plugin configuration supports custom context. You can include markdown formatting in the `.claude/plugin-name.local.md` body to provide additional instructions, prompts, or project-specific documentation alongside YAML settings.

Why should I use local config files instead of editing global plugin settings?▼

You should use local config files instead of global settings to prevent committing sensitive information and to ensure that custom plugin behavior remains isolated and does not affect other projects on your system.

Related Skills

Explore More Software Engineering Skills→
mazenyassergithubmazenyassergithub
6

omc-default

Configure oh-my-claudecode for a local project by creating a `.claude` directory and downloading `CLAUDE.md` from GitHub.

Community
Basic
angrybeaglesangrybeagles

plugin-settings

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

Community
Intermediate
VivekSinghRathore7VivekSinghRathore7

plugin-settings

Manage Claude Code plugin settings via YAML frontmatter and markdown files.

Community
Intermediate
ngxtmngxtm

Dart Best Practices

Enforce Dart purity standards for scoping, immutability, configuration, and naming.

Community
Basic