Plugins can remember their own settings for each project. This skill uses a special file called .claude/plugin-name.local.md to store configuration. The file has two parts: YAML frontmatter for structured settings and markdown content for extra context or instructions.
Developers of Claude Code plugins can use this pattern to make their plugins user-configurable. Settings like enabled, strict_mode, or max_retries are easy to read from hooks, commands, or agents. Each project can have its own setup without interfering with others.
This approach keeps plugin state files out of version control. They should be added to .gitignore. The markdown body can also hold prompts, notes, or contact info. It is a simple way to give plugins a memory per project.
Global
mkdir -p ~/.claude/skills/plugin-settingsProject
mkdir -p .claude/skills/plugin-settingsSource Repository
Setup Matt Pocock Skillsmattpocock/skills
Set up your repo for engineering skills with just a few guided steps
Lark Skill Makerlarksuite/cli
Create reusable skills to automate Feishu tasks with lark-cli commands
Teachmattpocock/skills
Teach yourself any skill with guided lessons and mission-driven practice
Write A Skillmattpocock/skills
Build new agent skills with clear structure and bundled resources
Writing Great Skillsmattpocock/skills
A guide for writing predictable AI agent skills with clear principles and reliable behavior
Ask Mattmattpocock/skills
Pick the perfect skill or flow for your project every time
Writing Skillsobra/superpowers
Test your agent skills like code to make them truly effective
Animejsheygen-com/hyperframes
Safely add Anime.js animations to your HyperFrames compositions with seek control