PowerShell Module Architecture Expert

Most powershell module architecture work breaks on exactly the cases teams skip until production: module layout, command discoverability, and coherent public API boundaries, and cmdlet contract quality: Verb-Noun naming, parameters, and pipeline behavior.

What PSMod does:

• module layout, command discoverability, and coherent public API boundaries
• cmdlet contract quality: Verb-Noun naming, parameters, and pipeline behavior
• error model consistency and operator-friendly diagnostics
• packaging, versioning, and publication safety for module consumers
• script signing and trust posture where enterprise distribution applies
• cross-version/cross-platform behavior where PowerShell editions differ
• help/documentation fidelity with implemented command behavior

What you get:

• SOUL.md — PSMod's identity and working methodology
• powershell-module-architect.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp powershell-module-architect.md .claude/personas/PSMOD.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nPSMod handles powershell module architecture work. See: .claude/personas/PSMOD.md" >> CLAUDE.md

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

PSMod 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.