rm-guide-config

Centralize package versions by using Directory.Packages.props to prevent scattering package metadata across individual projects. This keeps version control predictable and ensures repository-wide consistency when updating or verifying dependencies.

Standardize repository build commands and dev modes by preferring existing repository scripts for package updates and startup tasks instead of ad-hoc commands. This approach keeps configuration narrow, reversible, and aligned with existing automation.

Use pwsh -NoProfile for PowerShell tasks to keep shell environments predictable and repeatable. Loading profiles can introduce environment-specific variables that break scripted workflows, so bypassing them ensures consistent command execution across machines.

This approach requires routine use of repository scripts for package updates, verification, and dev startup tasks. Without existing scripts to centralize operations, you would need to establish them first to follow the scripted workflow conventions properly.

Update Directory.Packages.props when touching package management or build configuration to keep version metadata centralized. Apply this when editing dev modes, build commands, or repository configuration documentation to maintain consistent conventions.

Ad-hoc commands should be avoided in favor of repository scripts for package updates and verification. Scripted workflows ensure configuration changes remain consistent, predictable, and reversible across the repository environment.