Add PowerShell command generation rules

- Create new markdown file for PowerShell console command guidelines
- Define syntax and best practices for PowerShell 7 commands
- Provide comprehensive reference for Windows 11 PowerShell usage
- Highlight key differences from bash and cmd.exe syntax

Author: pstackebrandt

.cursor/rules/console-commands-for-powershell.mdc

@@ -0,0 +1,18 @@
+---
+description: PowerShell 7 Command Generation (Not Bash)
+globs: ["*.ps1", "*.psm1", "*.psd1", "*.md", "*.txt"]
+alwaysApply: true
+---
+
+When generating console commands, use PowerShell 7 syntax for Windows 11, NOT bash syntax. Remember these key differences:
+
+- Use PowerShell cmdlets like Get-ChildItem (not ls), Set-Location (not cd), etc.
+- Use backslashes for paths (C:\Users\) not forward slashes 
+- Command flags use hyphen prefix (-Force) not double-hyphen (--force)
+- Variables use $ prefix ($variable) and string interpolation uses "$()"
+- Environment variables use $env:VARIABLE format
+- Piping uses | operator but cmdlets expect specific object input
+- Command concatenation uses ; or separate lines, not && 
+- Redirection uses >, >>, 2> (not 2>&1)
+
+Always prefer PowerShell-native approaches over legacy cmd.exe commands.