settings▌

Plugins can store user-configurable settings and state in .claude/plugin-name.local.md files within the project directory. This pattern uses YAML frontmatter for structured configuration and markdown content for prompts or additional context.

Plugins can store user-configurable settings and state in .claude/plugin-name.local.md files within the project directory. This pattern uses YAML frontmatter for structured configuration and markdown content for prompts or additional context.

Analyze this repository and generate recommended Claude Code settings.json permissions for read-only commands.

Store per-project plugin configuration and state in .claude/plugin-name.local.md files with YAML frontmatter. \n \n Settings files use YAML frontmatter for structured configuration and markdown body for additional context or prompts \n Hooks, commands, and agents can read settings to customize behavior without requiring code changes \n Includes bash parsing patterns for extracting individual fields (strings, booleans, numerics) and markdown body content \n Common patterns include toggling hook a

Per-project plugin configuration stored in YAML frontmatter and markdown files within the .claude/ directory. \n \n Settings files use .claude/plugin-name.local.md format with YAML frontmatter for structured config and markdown body for additional context or prompts \n Hooks, commands, and agents can read settings to customize behavior; quick-exit pattern checks file existence and enabled flag to skip when not configured \n Parsing techniques provided for extracting individual fields (strings, b