14d • 🍺 Scuttlebutt
Rebuilding my CORE
quick one I thought the group might find useful.
Now that Fable 5 is staying on as my assistant, I had it map out something I'd only ever kept in my head: how Claude in Chrome and headless Playwright actually divide the work in my setup, and how the system decides which one to reach for on any given job.
The short version is that it stopped being a "which tool is better" question. They're two engines for two kinds of work. Anything hands-on — verifying a deploy, checking a page behind my own logins, a client walkthrough — runs through Claude in Chrome. Anything unattended and repeating — my scheduled monitoring, research pulls, bulk work — runs on Playwright, because Chrome can't sit in that seat at all. Build on one, ship on the other.
The attached brief lays it out against my real workflows, plus a section on how the same split turns into client offerings. Thought it might be of interest.
2
0 comments
Rebuilding my CORE
powered by
skool.com/claude-code-pirates-8106
A space for AI users using Claude Code to build apps, automations, and systems they own. No hype.
Suggested communities
Powered by