jungho-git/pwsh

PowerShell

• Shared examples and formatting reference: references/EXAMPLE.md.
• Keep new guidance, snippets, and edits aligned with that file.

Scope

Use this rule when:

• editing .ps1 scripts
• composing native command calls from PowerShell
• handling filesystem paths, arguments, environment variables, and exit codes
• structuring numbered script sections

PowerShell should orchestrate commands with paths and arguments treated as data.

File Operation Boundary

• Use fs-mcp first for local file reads, writes, edits, listings, metadata, and search.
• Do not use Get-Content, Set-Content, Add-Content, Out-File, or redirection operators for local file processing.
• Use Bun file APIs only when fs-mcp cannot reasonably achieve the goal.
• State the fallback reason before using another runtime or API.

Command Rules

• Prefer Join-Path, Split-Path, and path helpers over manual string concatenation.
• Invoke native commands directly with & and separated arguments.
• Never use Invoke-Expression.
• Check $LASTEXITCODE after native commands when relevant.
• Fail clearly on missing files, invalid paths, invalid arguments, or missing tools.
• Never use C-style index-based for loops; use foreach or pipeline iteration.

Script Shape

• Wrap grouped script-level statements inside & { ... } when the file uses section blocks.
• Use $global: state only when shared across numbered setup sections or class methods.
• Do not leave shared state in bare variables when local convention uses $global: initialization blocks.
• When generating new code, keep newly authored constant and variable names at 30 chars or fewer by default; alias external contract names locally when needed.
• Extract functions only for real duplication, a large cohesive responsibility, or a boundary.

Formatting

• Use Stroustrup clause layout for else, elseif, catch, and finally.
• Always use braces for if, else, elseif, foreach, for, and while bodies.
• Prefer early returns.
• Use exactly one space around binary operators.
• Never vertically align assignments, parameters, or hash-table values.
• When paired section rulers are used, the section body starts with & { immediately after the bottom ruler.

Validation Focus

• parser validity
• path handling correctness
• native command argument boundaries
• exit-code handling
• section block integrity and $global: state visibility