What problem does it solve? On Windows 11 with Traditional Chinese locale (CP950/Big5), PowerShell 5.1 silently corrupts Chinese text: scripts saved without BOM fail to dot-source, console output shows ??, JSON IPC breaks, and Start-Process truncates Chinese arguments. This Skill provides a complete set of defensive encoding rules to eliminate mojibake and silent failures. ## Core Features & Use Cases - Mandatory Script Header: A three-line UTF-8 initialization block placed after param(), plus UTF-8 with BOM file saving so PS 5.1 parses scripts correctly. - Safe File I/O Helpers: Read-Utf8File, Write-Utf8File, Read-JsonFile, and Write-JsonFile replace Get-Content/Set-Content to avoid Big5 misreads and JSON BOM errors. - IPC and Process Safety: Correct Stop Hook stdin reading via [Console]::In.ReadToEnd(), and passing long Chinese prompts to the Claude CLI through @tempfile instead of Win32 ANSI arguments. - Dangerous Character Blacklist: Replacements for em dash, box-drawing characters, curly quotes, and full-width spaces that Big5 cannot represent, enforced by a CI guard script. - Use Case: When writing or reviewing any .ps1 in the party-to-pipeline (orchestrator, workers, shared-utils, stop-report), apply this Skill so Chinese log output, JSON task files, and spawned Claude processes all handle UTF-8 correctly. ## Quick Start Ask the AI to review your PowerShell script for Windows Traditional Chinese encoding issues and apply the UTF-8 header, safe file I/O helpers, and dangerous character replacements.
