maintaining-windows-health

# Maintaining Windows 11 Health Recovery and prevention playbook for Windows 11 disk and memory crises. A Windows port of the `maintaining-macos-health` skill: same three layers (triage → tiered recovery → automation/alerting) and the same safety invariant — **scan → JSON → user picks in a UI → apply deletes only what was picked** — but with Windows-native tooling and Windows-specific "never touch" rules. The same playbook works for routine cleanup or first-time setup on a new machine. ## Table of contents - [When to use](#when-to-use) - [Skill layout](#skill-layout) - [Core mental model](#core-mental-model) - [Standard workflows](#standard-workflows) - [A. "Free space NOW" (incident response)](#a-free-space-now-incident-response) - [B. "Set up alerting" (new machine or first time)](#b-set-up-alerting-new-machine-or-first-time) - [C. Alerter stopped working / making noise](#c-alerter-stopped-working--making-noise) - [D. "Uninstall an app cleanly"](#d-uninstall-an-app-cleanly) - [Safety rules (non-negotiable)](#safety-rules-non-negotiable) - [Domain quirks captured](#domain-quirks-captured) - [Outcomes scale](#outcomes-scale) ## When to use Trigger on any of: - Disk free < 20 % or user complains about being out of space - BSOD / unexpected reboot / Kernel-Power 41 / WHEA error / a new crash dump in `C:\Windows\Minidump` - "PC is slow", commit pressure high (`% Committed Bytes In Use` > 85), pagefile growing - User wants to set up monitoring/alerting from scratch ...