package-namespace-migration

Namespace shadowing happens when BeginPackage removes the original package from $ContextPath, allowing usage-only symbols to override real implementations. This Skill prevents this by enforcing phase-appropriate usage declaration rules and namespace-qualified definitions during context migration.

You can safely migrate functions by applying phased migration patterns: namespace reservation, full transfer, and wrapper/alias sequencing during deprecation. This Skill validates your BeginPackage and Remove sequences to ensure context-path behavior remains stable across package boundaries.

The best way to prevent self-recursion is to apply correct Remove and alias sequencing rules during context migration. This Skill flags failure patterns like usage-only shadowing and DAG handler breakage, enforcing namespace-qualified definitions to avoid unintended recursion.

Yes, you can use deprecation wrappers while keeping infrastructure working by applying Phase C migration patterns. This Skill ensures context-path stability and safe alias sequencing so existing public APIs remain functional across reorganized package boundaries.

No, turning off General::shdw warnings makes diagnosis harder by hiding shadowing root causes. This Skill identifies why suppressing shadowing warnings obscures context-resolution failures and instead enforces proper usage declaration rules to prevent shadowing proactively.

You should not use standard BeginPackage refactoring without phase-appropriate usage declarations when migrating existing public symbols. This Skill flags cases where declaring usage for an existing symbol risks context-path shadowing, preventing hard-to-debug breakages during package reorganization.