If you spend any meaningful part of your week writing PowerShell, there is a good chance you are still solving the same class of problems you solved five years ago — just with slightly different cmdlets. Claude can cut the time you spend on boilerplate, syntax lookups, and debugging in half. This is not about replacing your expertise; it is about removing the friction around it.
The Right Mental Model
Think of Claude as a very fast junior who has read every Microsoft docs page, Stack Overflow thread, and GitHub gist ever written. You still need to review what it produces, but you no longer need to write the first draft yourself or remember the exact syntax for Select-Object -ExpandProperty
Prompt Patterns That Work
Vague prompts produce vague code. These patterns consistently give useful output for IT tasks:
# Be specific about input and output
# WEAK: "write a script to find inactive users"
# STRONG: "Write a PowerShell script using Microsoft.Graph that finds all Entra ID users
# with no sign-in for 90+ days. Output CSV: UPN, DisplayName, LastSignIn,
# AccountEnabled. Use -Filter to avoid loading all users into memory."
# Always include your environment constraints:
# "Runs as a service account via Task Scheduler on Server 2022.
# Cannot use interactive auth. Use certificate-based app registration."
# Ask for error handling explicitly:
# "Add try/catch around Graph calls and write failures to a separate error log CSV."Debugging: Paste the Error, Get the Fix
When a script fails, paste the full error message plus the relevant code block. Include your PowerShell version and module versions — many errors are environment-specific and Claude will catch that immediately.
$PSVersionTable | Select-Object PSVersion, OS
Get-Module Microsoft.Graph -ListAvailable | Select-Object Name, Version
# Then paste your error. Example:
# "Get-MgUser : The request is invalid. Filter contains unsupported value."
# Claude will spot that Graph uses OData $filter syntax, not AD-style LDAP filters,
# and rewrite the -Filter expression correctly.Modernising Old Scripts
Paste a working but messy script and ask Claude to: add comment-based help, replace deprecated cmdlets, convert Write-Host to proper logging, or make it pipeline-friendly. A 200-line script from 2018 can be modernised in minutes.
# Sample prompt:
# "Refactor this script to:
# 1. Use splatting instead of long parameter lines
# 2. Replace Write-Host with Write-Verbose and Write-Warning
# 3. Add [CmdletBinding()] and param() block with validation
# 4. Make it accept pipeline input for -ComputerName
# [paste code]"The One Habit That Saves the Most Time
Keep a Claude conversation open while you work. When you hit friction — an unfamiliar API endpoint, a regex that is not working, a filter not returning what you expect — paste it in immediately rather than spending 20 minutes on documentation. Over a week, that single habit typically saves two to three hours of context-switching.
Summary
The biggest efficiency gain is not any single technique — it is reaching for Claude before you reach for documentation. Combine specific prompts, environment context, and a review step, and you will ship cleaner scripts faster than you ever have.
