What problem does it solve? Editing a dotfiles repository without knowing which files are symlinked by GNU Stow versus managed by setup scripts leads to broken links, lost runtime state, and unsafe changes to a live home directory. ## Core Features & Use Cases - Ownership Map: Explains that stow/<package>/ mirrors $HOME paths owned exclusively by GNU Stow, while setup/ scripts handle mutable state like Pi settings, Cursor hooks, Zed settings, and Paseo plugins. - Profile Guidance: Documents the macos, linux, wsl, server, and cloudbro profiles and the stow.sh plan/apply/remove and install.sh commands. - Safety Protocol: Enforces previewing with ./stow.sh plan, testing with an isolated STOW_TARGET, never using stow --adopt on a real HOME, and verifying every managed link resolves inside the repository. - Use Case: Before adding a new shell configuration, consult this Skill to decide whether it belongs in a Stow package or a setup script, then preview and apply the change safely. ## Quick Start Ask the assistant to explain where a new configuration file belongs in the dotfiles repo and how to apply it with the correct profile.