PowerShell Engineering

Use this skill when the repo contains .ps1, .psm1, or .psd1 files, or when the task involves automation, administration, CI scripting, or Windows-focused tooling.

Primary rule sources

• rules/common/coding-style.md
• rules/common/patterns.md
• rules/common/testing.md
• rules/common/security.md
• rules/common/hooks.md
• rules/powershell/coding-style.md
• rules/powershell/patterns.md
• rules/powershell/testing.md
• rules/powershell/security.md
• rules/powershell/hooks.md

Seeded references

• knowledge-bases/seeded/powershell/docs/overview.md
• knowledge-bases/seeded/powershell/docs/review-checklist.md
• knowledge-bases/seeded/powershell/docs/frameworks.md
• knowledge-bases/seeded/powershell/examples/

Supplemental engineering references

• skills/powershell-engineering/references/repo-exploration.md
• skills/powershell-engineering/references/output-templates.md
• skills/powershell-engineering/references/agent-patterns.md
• skills/powershell-engineering/references/debugging-playbook.md
• skills/powershell-engineering/references/scripting-and-modules.md
• skills/powershell-engineering/references/remoting-and-ops.md
• skills/powershell-engineering/references/testing-and-ci.md
• skills/powershell-engineering/references/examples.md

Assistant expectations

• write scripts that are explicit, safe, and compatible with modern PowerShell
• favor parameterized commands, clear output, and idempotent automation
• apply the review checklist before completing operational scripts
• use the seeded examples to shape module, CI, and bootstrap flows