提示词如下：

Please strictly adhere to the following rules:  
1. Check first, then execute. First scan disk usage, list large directories, large files, cache directories, download directories, duplicate backups, old installation packages, video materials, logs, temporary files. Focus on scanning and listing the following high-frequency space hogs: local large model caches (such as ~/.cache/huggingface or .ollama), Python pip/conda caches, Node.js caches, and WSL/Docker virtual disk images (such as ext4.vhdx—only list their sizes, absolutely do not operate on them). Do not generate any deletion or movement scripts before completing the check.

2. Safety first—better to clean less than to take risks. By default, only handle "regenerable caches, temporary files, logs, crash dumps, obvious user data copies, old backups, downloaded installation packages, large media files." Prioritize "moving to another drive," and only then "deleting." Do not touch anything that might affect the system, development environment, trading programs, or software operation.

3. Strictly prohibit direct handling of the following locations unless I explicitly name and authorize them: - Windows / System32 / SysWOW64 - Program Files / Program Files (x86) - ProgramData - Unclear content in system configuration directories under Users (strictly prohibit touching specific software configuration directories under AppData\Roaming and AppData\Local, such as VS Code, browser data, etc., except for AppData\Local\Temp) - Registry, drivers, startup items, service-related files - Databases, development environments, IDE configurations, browser user profiles, chat histories, cloud sync directories - Any directories currently in use by programs - Any symbolic links, junctions, mount points, reparse points  

4. For each candidate item, classify it first: - A Category: Safe to delete   For example: temporary files in Temp, caches, CrashDumps, DXCache, useless logs, thumbnail caches, etc. - B Category: Safe to move and create a link   For example: large model caches, downloaded installation packages, old backups, video materials, compressed archives, exported project files, etc. - C Category: Risky, prohibit automatic handling   For example: program data, sync directories, databases, browser profiles, chat software data, WSL/virtual machine images currently in use, etc.  

5. Before execution, you must first provide me with a "cleanup plan," in the fixed format below: - Path - Size - Type (delete/move/skip) - Reason - Risk level (low/medium/high) - Whether my confirmation is needed  

6. Without my confirmation, do not plan to execute "medium-risk" or "high-risk" operations. Only "low-risk and clearly regenerable" content can be included in the automatic execution plan. If uncertain, stop and ask me.  

7. Script generation and rollback capability: You cannot directly operate on the disk; you must output safe, standardized PowerShell scripts for me to execute. 
• When moving files, prioritize moving to [target drive path] and retain a clear directory structure. - Safe mapping scheme: For B-category items that need to be compatible with the original path, use `cmd /c mklink /J "original path" "new path"` in the PowerShell script to create a directory junction (Directory Junction)—absolutely prohibit using ordinary shortcuts (.lnk).

Before creating the link, the script must include logic to verify that the target path has been successfully copied. - Before deletion operations, first tally the size and record the path. The script must include error handling (Try-Catch) and absolutely avoid irreversible bulk dangerous commands (such as unrestricted wildcards). - Do not empty the Recycle Bin unless I explicitly request it.  

8. After execution, you must review and report (please include logic in the script you provide me to output the following report information): - Available space on each disk before and after cleanup - Which directories were actually moved - Which directories were actually deleted - Which high-risk items you deliberately left untouched - Whether there are any items that require my manual decision 

 9. Output language must use Chinese, explanations should be concise and clear, and do not just provide commands without explanation.  
My current goal is: 
• System drive: [e.g., C drive] 

• Target drive: [e.g., E drive]

• Request: Release as much space as possible, but absolutely do not affect the normal operation of the system, development environment, and commonly used software.

中文提示词：

请严格遵循以下规则：
先检查，后执行。​ 首先扫描磁盘使用情况，列出占用空间大的目录、大文件、缓存目录、下载目录、重复备份、旧安装包、视频素材、日志、临时文件。重点扫描并列出以下高频空间占用源：本地大模型缓存（如 ~/.cache/huggingface 或 .ollama）、Python pip/conda 缓存、Node.js 缓存、以及 WSL/Docker 虚拟磁盘镜像（如 ext4.vhdx——仅列出大小，绝对不要对其进行任何操作）。在完成检查前，不得生成任何删除或移动脚本。
安全第一，宁少勿错。​ 默认只处理“可再生的缓存、临时文件、日志、崩溃转储、明显的用户数据副本、旧备份、已下载的安装包、大型媒体文件”。优先选择“移动到其他驱动器”，其次才是“删除”。严禁触碰任何可能影响系统、开发环境、交易程序或软件运行的内容。
除非我明确指名授权，否则严格禁止直接处理以下位置：
Windows / System32 / SysWOW64
Program Files / Program Files (x86)
ProgramData
Users 目录下系统配置目录中内容不明的部分（严格禁止触碰 AppData\Roaming 和 AppData\Local 下的特定软件配置目录，如 VS Code、浏览器数据等，AppData\Local\Temp 除外）
注册表、驱动、启动项、与服务相关的文件
数据库、开发环境、IDE 配置、浏览器用户配置文件、聊天记录、云同步目录
任何正在被程序使用的目录
任何符号链接、Junction 交叉点、挂载点、重新解析点（reparse points）
对每个候选清理项，先进行安全分类：
A 类（Category A）：可安全删除
例如：Temp 中的临时文件、各类缓存、CrashDumps、DXCache、无用日志、缩略图缓存等。
B 类（Category B）：可安全移动并创建链接
例如：大模型缓存、已下载的安装包、旧备份、视频素材、压缩归档、导出的项目文件等。
C 类（Category C）：高风险，禁止自动处理
例如：程序数据、同步目录、数据库、浏览器配置文件、聊天软件数据、正在使用的 WSL/虚拟机镜像等。
执行前，必须先提供一份“清理计划”，格式固定如下：
路径
大小
类型（删除 / 移动 / 跳过）
原因
风险等级（低 / 中 / 高）
是否需要我确认
未经我确认，不得计划执行“中风险”或“高风险”操作。​ 只有“低风险且明确可再生”的内容才能纳入自动执行计划。如有不确定之处，立即停止并询问我。
脚本生成与回滚能力：你不能直接操作磁盘，必须输出安全、规范的 PowerShell 脚本供我执行。
移动文件时，优先移动到 [目标驱动器路径]，并保留清晰的目录结构。
安全映射方案：​ 对于需要兼容原路径的 B 类项目，在 PowerShell 脚本中使用 cmd /c mklink /J "原始路径" "新路径" 创建目录交接点（Directory Junction）——严禁使用普通的快捷方式（.lnk）。
创建链接前，脚本必须包含验证目标路径已成功复制的逻辑。
删除操作前，先统计大小并记录路径。脚本必须包含错误处理（Try-Catch），绝对避免不可逆的批量危险命令（如不加限制的通配符）。
除非我明确要求，否则不要清空回收站。
执行后，必须审查并汇报（请在提供的脚本中加入输出以下报告信息的逻辑）：
清理前后各磁盘的可用空间
实际移动了哪些目录
实际删除了哪些目录
哪些高风险项被你刻意保留未动
是否有需要我手动决定的项目
输出语言必须使用中文，解释应简明扼要，不要只给命令而不做说明。
我的当前目标是：
系统盘：[例如 C 盘]
目标盘：[例如 E 盘]
诉求：尽可能释放空间，但绝对不能影响系统、开发环境和常用软件的正常运作。