plugin-settings

Manage per-project plugin configurations using `.claude/plugin-name.local.md` files with YAML frontmatter.

Updated Jan 11, 2017
One-click install
npx skills add https://github.com/kaustubhhiware/dotfiles --skill plugin-settings-kaustubhhiware
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/kaustubhhiware/dotfiles/tree/main/claude/plugins/marketplaces/claude-plugins-official/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/kaustubhhiware/dotfiles --skill plugin-settings-kaustubhhiware

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 per-project customization of plugin behavior, allowing users to store and manage specific configurations without altering global settings or committing sensitive information to version control.

Core Features & Use Cases

  • Per-Project Configuration: Define unique settings for each project using .claude/plugin-name.local.md files.
  • YAML Frontmatter: Structure settings using YAML for easy parsing.
  • Markdown Body: Include additional context, prompts, or documentation within the settings file.
  • Use Case: A developer can configure a linter plugin to use a stricter rule set for a critical project by creating a .claude/linter.local.md file, while using default settings for other projects.

Quick Start

Create a new file named .claude/my-plugin.local.md in your project's root directory and add your custom settings within the YAML frontmatter.

Frequently Asked Questions about plugin-settings

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

FAQPage Schema
How do I manage local plugin configurations for individual projects?

You can manage per-project plugin configurations by creating `.claude/plugin-name.local.md` files with YAML frontmatter and markdown bodies. This approach isolates settings per project and keeps them gitignored.

Can I use YAML frontmatter for per-project plugin settings?

Yes, YAML frontmatter structures custom settings within `.claude/plugin-name.local.md` files. This format separates machine-readable configuration from human-readable markdown documentation.

What is the best way to keep sensitive plugin settings out of version control?

Storing configurations in `.claude/plugin-name.local.md` files keeps sensitive settings out of version control. These files are user-managed and gitignored, preventing accidental commits.

How do hooks and commands read dynamic plugin configurations?

Hooks and commands read settings from the `.claude/plugin-name.local.md` files to adapt behavior dynamically. This allows custom configurations to modify plugin execution on a per-project basis.

Does this per-project configuration approach work without altering global settings?

Yes, using `.claude/plugin-name.local.md` files modifies behavior only for the current project. Global settings remain untouched, allowing default rules to apply elsewhere.

When do I need a local markdown file for plugin configuration?

You need a local markdown file when customizing plugin behavior for a specific project, like applying stricter linter rules. It provides isolated, project-specific overrides without affecting global defaults.