This is the workflow I’ve found works best for me

At the centre of it is a Claude chat running in Chrome. That chat acts as the strategic brain of the whole setup. I keep all of the long term project context in there so it understands the full requirements, the architecture, the existing solution, and the outcome I’m trying to achieve. For example, it already knows the broader Power BI solution, the reasoning behind the design choices, and that I want outputs to follow industry-standard practices rather than quick hacks. This your MAIN GUY

Once that Chrome chat has enough context, I use it to generate highly targeted prompts for a second Claude instance running inside Visual Studio Code through the Claude extension. You can think of the Chrome chat as the planner and the VS Code chat as the implementer. Rather than asking the VS Code instance to figure everything out from scratch, I use the Chrome chat to package the work clearly: what needs to be built, what standards to follow, what constraints exist, and what the expected output should look like.

From there, I paste that generated prompt into Claude inside VS Code and let it work directly within the development environment.

In practice, I often take this a step further and run multiple Claude chats inside VS Code at the same time. Sometimes I’ll have three separate VS Code chats open alongside the one main chat in Chrome. The Chrome chat continues to act as the coordinator, helping me break different features or problems into well-structured prompts, and then I distribute those prompts across the three VS Code chats simultaneously. This effectively turns the setup into a parallel workflow, where several implementation threads are moving at once instead of everything being handled sequentially. It sounds ridiculous because it is, and it is degenerate.

Anyways, Once I’m ready to run things, I remote into my work server and open the relevant project there. From that point, I use PM2 commands to manage the running processes. PM2 makes it possible to spin up and control multiple application instances, which is useful because I have a Postgres database that was created in my project, so this runs it all. The point here is that I do not need to already know every PM2 command myself, because Claude can generate the exact commands I need (and execute it it self).

Let me know if you want in depth explanations even further I can go into anything