skills.rest
liminal-ai
liminal-aiOFFICIAL
Explore all skills by this author →
GitHub

plugin-settings

Centralize per-project plugin configuration using YAML frontmatter in local files.

Updated Mar 16, 2026
Search Tags:#hooks#claude#configuration#yaml#frontmatter#gitignore#plugin-settings
One-click install
npx skills add https://github.com/liminal-ai/code-steward --skill plugin-settings-liminal-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/liminal-ai/code-steward/tree/main/.claude/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/liminal-ai/code-steward --skill plugin-settings-liminal-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Traditional plugin configurations are often global or scattered, making it hard to apply per-repository settings and track changes. This Skill provides a standardized pattern to store per-project plugin configuration as YAML frontmatter within .claude/plugin-name.local.md files, keeping configuration local and gitignored.

Core Features & Use Cases

  • Per-project configuration stored in .claude/<plugin-name>.local.md with YAML frontmatter and markdown body to separate structure from prompts.
  • Supports enabling/disabling plugins per project, default values, and per-project state or prompts that survive across sessions.
  • Works with hooks, commands, and agents to adapt behavior to the current repository, without altering global defaults.

Quick Start

Create .claude/plugin-name.local.md with YAML frontmatter and a Markdown body to configure the plugin for this project.

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 in Claude without affecting global defaults?▼

Per-project plugin configuration is managed by creating .claude/plugin-name.local.md files with YAML frontmatter to store repository-specific settings, keeping local configurations gitignored and separate from global defaults.

What is YAML frontmatter used for when configuring repository hooks and agents?▼

YAML frontmatter separates structured configuration data from markdown prompt text in local settings files. This mechanism enables safe defaults, atomic updates, and per-project state storage that survives across sessions for hooks and agents.

How do I set up gitignore practices for local Claude configuration files?▼

Gitignore practices for local Claude configuration involve keeping .claude/plugin-name.local.md files untracked by version control. This ensures per-repository settings and state storage remain isolated without altering shared project defaults.

Can I enable or disable specific plugins per repository?▼

Plugins can be enabled or disabled per repository by defining the status within the YAML frontmatter of the project-specific .claude/plugin-name.local.md file. This overrides global behavior for the current working repository only.

What's the best way to store per-project state and prompts that survive across sessions?▼

The best way to store per-project state and prompts is using YAML frontmatter in local markdown files. This pattern provides structured parsing, safe defaults, and atomic updates to ensure settings persist reliably across sessions.

Related Skills

Explore More Software Engineering Skills→
ahandselahandsel
1

sync-skill-allowlist

Synchronize skill entries in project settings against repository SKILL.md files.

Community
Intermediate
AVVlasovAVVlasov

plugin-settings

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

Community
Intermediate
fcakyonfcakyon
1.0k

plugin-settings

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

Community
Intermediate
kenkenmainkenkenmain
1

configuration

Load, merge, and validate subagents configuration from global and project files.

Official
Advanced