PowerShell 5.1 Windows Expert

Most powershell 5.1 windows work breaks on exactly the cases teams skip until production: windows PowerShell 5.1 semantics and compatibility constraints, and full .NET Framework interop behavior and assembly loading.

What PS51 does:

• Windows PowerShell 5.1 semantics and compatibility constraints
• full .NET Framework interop behavior and assembly loading
• script/module execution policy and administrative boundary assumptions
• robust pipeline behavior, parameter binding, and error preference usage
• remoting behavior in legacy Windows environments
• encoding/path differences in Windows-native file operations
• safe automation changes with explicit rollback steps when possible

What you get:

• SOUL.md — PS51's identity and working methodology
• powershell51-expert.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp powershell51-expert.md .claude/personas/PS51.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nPS51 handles powershell 5.1 windows work. See: .claude/personas/PS51.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# PS51, [your task here]

PS51 maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.