mde-package-cache-policy
Cross-ecosystem cache policy for mise-managed tooling, including preferred cache locations, warming, reuse, and bounded pruning rules.
SKILL.md.agents/skills/mde-package-cache-policy/SKILL.md
GitHubMDE Package Cache Policy
Use this skill when changing setup, migration, verification, automation, or host-tool cache behavior.
Preferred Cache Locations
UV_CACHE_DIR:~/Library/Caches/uvon macOS,~/.cache/uvelsewhere.PIPX_HOME:~/.local/pipxPIPX_BIN_DIR:~/.local/binBUN_INSTALL:~/.bunGOCACHE:~/Library/Caches/go-buildon macOS,~/.cache/go-buildelsewhere.GOMODCACHE:~/go/pkg/modCARGO_HOME:~/.cargoRUSTUP_HOME:~/.rustup
Policy
- Reuse backend-native caches by default.
- Warm caches with declarative
mise install,mise run, or backend-native read-only commands. - Do not delete caches during normal setup, verification, or automation.
- Cache pruning is allowed only in bounded maintenance flows with explicit commands such as
uv cache prune,bun pm cache rm, orgo clean -cache -modcache. - Record cache behavior in
configs/mde-modernization-matrix.jsonand never rely on shell-only tribal knowledge.
cache pruning
- cache pruning is never the default path.
- cache pruning must be explicit, bounded, and recorded in maintenance guidance.
Drift Rules
- Treat hardcoded alternate cache paths as drift unless the matrix or exception registry declares them.
- Treat cold-install guidance as drift unless an exception explicitly allows it.
- Preflight should verify cache directories are writable before automation starts.