package-namespace-migration

What problem does it solve?

This Skill prevents hard-to-debug breakages caused by Mathematica context-resolution and BeginPackage behavior when moving public functions from one package context to another, specifically avoiding unintended symbol shadowing.

Core Features & Use Cases

• Explains the shadowing root cause: how BeginPackage without the right dependency context path can temporarily remove the original package from $ContextPath and cause usage-only symbols to override real implementations.
• Provides phase-based safe migration patterns: Phase Q-2a (namespace reservation), Phase Q-2b (full transfer), and Phase C (wrapper/alias during deprecation).
• Includes concrete failure-mode lessons: covers real failure patterns (self-recursion, usage-only shadowing, and why Off[General::shdw] makes diagnosis harder).
• Use case: migrate claudecode-related functions into a new Mathematica package context (e.g., splitting claude code management into ClaudePackageManager), while keeping LLMGraphDAGCreate and related infrastructure working.

Quick Start

Ask an AI assistant to review your planned BeginPackage/Remove/migration sequence against the package-namespace-migration skill’s Phase A/B/C patterns and to flag any cases where you would declare usage for an existing public symbol or risk context-path shadowing.