When you build a PowerShell project from multiple files, the natural structure is clear: enums first, then classes, then functions. Each group has its own place, and as long as dependencies only flow in one direction, that structure works perfectly. But sometimes a function depends on a class, and that class calls the function. There is no longer a clean boundary between the two groups — they need
Most of the "I built an AI workflow" posts you see on here treat Claude like a fancy text box. Open chat, paste prompt, copy answer, ship. That's fine for solo dev tasks. It falls apart fast when you start building for someone else's business, especially one with strict confidentiality, compliance baggage, and a workflow that runs on documents. I've been building Claude-powered tooling for law fir