_gobbi-rule-container

To distribute Claude behavioral rules consistently, place `_gobbi-rule.json` and `_gobbi-rule.md` in a plugin container that symlinks them into `.claude/rules/` at session start. This ensures automated rule delivery without manually loading files into agents.

Managing rule files in a Claude plugin deployment is best handled by a central container holding `_gobbi-rule.json` and `_gobbi-rule.md`, which automatically symlinks updates into the `.claude/rules` runtime directory at session start.

Symlink rule mapping at Claude session start works by automatically linking core behavioral rule files from a plugin distribution location directly into the `.claude/rules/` directory, exposing runtime access without loading rules into agents.

Yes, you need `_gobbi-rule.json` and `_gobbi-rule.md` placed in the skill root directory to set up rule management for Claude plugins. These files act as the source of truth for behavioral rules distributed via symlinks.

Claude plugin rules may not update across sessions if the startup symlink mechanism is missing or if `_gobbi-rule.json` and `_gobbi-rule.md` are absent from the skill root, preventing automated mapping into `.claude/rules`.

Yes, you can keep rule content in the plugin source while accessing it at runtime in Claude. The container symlinks the source files into `.claude/rules/` at session start, maintaining the source of truth inside the plugin without loading rules into agents.