jimmy-core-preferences

You can consolidate Claude preferences into a single auto-loading source of truth to maintain consistency across multiple projects and sessions, eliminating repetition and enforcing unified behavior automatically.

The best way to stop repeating instructions is to use a master skill that applies permanent preferences and proactive context management, automatically loading your operating rules on session initialization.

No dependencies are required. The preferences routing system operates independently using internal multi-tier loading and HUB_MAP-driven routing to activate sub-skills without external packages.

Session memoria integration captures context and workflow patterns during active conversations, feeding a self-learning mechanism that updates your permanent preferences for future cross-project application.

Yes, you can track and audit changes to Claude operating rules using the built-in Git-backed update system, which provides version control and synchronizes policy updates across devices automatically.

If sub-skills become out of sync, strict governance enforces zero-tolerance for orphaned assets, automatically identifying and resolving mismatches to keep your master preference profile fully synchronized.