You can add settings to your own Claude plugins using a simple file. This file goes in the .claude folder and has a special name like plugin-name.local.md. It uses YAML frontmatter to store things like on or off, mode, or numbers. The rest of the file holds extra instructions or notes. This pattern is great for making plugins work differently in each project.
Developers can read these settings from bash scripts or from plugin commands. For example a hook can check if a plugin is enabled and then act accordingly. Parsing the YAML frontmatter is easy with simple commands like sed and grep. This gives you a flexible way to let users configure your plugin without changing code.
Remember to add this file to .gitignore so each developer can have their own settings. This keeps project configuration personal and safe. Using this pattern helps you build plugins that are both powerful and easy to adjust.
Global
mkdir -p ~/.claude/skills/plugin-settingsProject
mkdir -p .claude/skills/plugin-settingsSource Repository
Lark Skill Makerlarksuite/cli
Create reusable skills to automate Feishu tasks with lark-cli commands
Setup Matt Pocock Skillsmattpocock/skills
Set up your repo for engineering skills with just a few guided steps
Write A Skillmattpocock/skills
Build new agent skills with clear structure and bundled resources
Writing Skillsobra/superpowers
Test your agent skills like code to make them truly effective
Teachmattpocock/skills
Teach yourself any skill with guided lessons and mission-driven practice
Animejsheygen-com/hyperframes
Safely add Anime.js animations to your HyperFrames compositions with seek control
Contribute Catalogheygen-com/hyperframes
Turn your idea into a new HyperFrames registry block or component
Teach Impeccablepbakaus/impeccable
Old command renamed to /impeccable teach. Use that one instead