skills.rest
ffalor
ffalorCOMMUNITY
Explore all skills by this author →
GitHub

plugin-settings

Store and retrieve per-project plugin configuration using YAML frontmatter in markdown files.

1|Updated Feb 2, 2026
Search Tags:#developer tools#customization#yaml frontmatter#local state#plugin configuration#per-project settings
One-click install
npx skills add https://github.com/ffalor/agentic-coding --skill plugin-settings-ffalor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/ffalor/agentic-coding/tree/main/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/ffalor/agentic-coding --skill plugin-settings-ffalor

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a standardized pattern for managing per-project plugin configurations and state, allowing plugins to adapt their behavior based on the specific project context without requiring global changes.

Core Features & Use Cases

  • Per-Project Configuration: Store settings in .claude/plugin-name.local.md files within your project.
  • Dynamic Behavior: Hooks, commands, and agents can read these settings to customize their actions.
  • State Management: Persist plugin state across sessions for specific projects.
  • Use Case: A linter plugin can read a .claude/linter.local.md file to apply project-specific linting rules, ignore patterns, or enable/disable certain checks.

Quick Start

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

Frequently Asked Questions about plugin-settings

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

FAQPage Schema
How do I manage per-project plugin configuration without global settings?▼

Per-project plugin configuration is managed by storing YAML frontmatter settings in markdown files within the `.claude/` directory. This isolates plugin behavior to specific projects without global changes.

What is the best way to persist plugin state across sessions for a specific project?▼

Persist plugin state by storing it in `.claude/plugin-name.local.md` files using YAML frontmatter. The plugin reads and writes this local state file to maintain continuity across sessions.

How do hooks and agents customize behavior based on local project settings?▼

Hooks, commands, and agents parse YAML frontmatter from `.claude/plugin-name.local.md` files to dynamically adapt their actions. They read the parsed configuration to apply project-specific rules.

Can I use YAML frontmatter in markdown files to configure plugin options per project?▼

Yes, YAML frontmatter in local markdown files stores user-configurable plugin options. The plugin parses these files to retrieve project-specific configuration values.

Do I need to create a specific file structure for local plugin settings?▼

Yes, you create a `.claude/my-plugin.local.md` file in your project root. This specific directory and file naming pattern is required for the plugin to locate and parse the settings.

When should I use local state files instead of global plugin configuration?▼

Use local state files when plugins need to adapt behavior to specific project contexts without affecting other projects. Global configuration applies uniform settings everywhere.

Related Skills

Explore More Software Engineering Skills→
elct9620elct9620
9

Create Claude Plugin

Create a Claude plugin scaffold with configuration files and overwrite checks.

Community
Intermediate
fcakyonfcakyon
1.0k

plugin-settings

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

Community
Intermediate
jorgeasaurusjorgeasaurus
12

ckm:slides

Generate HTML presentations with Chart.js visualizations and design tokens.

Community
Intermediate
onesmartguyonesmartguy
2

secrets-management

Manage sensitive credentials securely across CI/CD pipelines and secret stores.

Community
Advanced