TCTestBot Chroniclesintestbot-chronicles.hashnode.dev·Apr 13 · 9 min readBehavorial contract part IV : the Assembled FrameworkThe previous three articles covered the pieces in isolation. Behavioral pillars that shape how Claude works. Adaptive complexity that decides how much process a task gets. A pipeline that enforces bra00
TCTestBot Chroniclesintestbot-chronicles.hashnode.dev·Apr 13 · 10 min readBehavorial contract part III : the pipeline behind the codeThe Pipeline Behind the Code Most conversations about AI-assisted coding focus on the moment Claude writes a function. The prompt, the output, the quality of the generated code. That moment matters, b00
TCTestBot Chroniclesintestbot-chronicles.hashnode.dev·Apr 13 · 8 min readBehavioral contract part II : not everything deserves a planLast month I watched Claude Code spend four minutes analyzing naming conventions, weighing three alternative approaches, and producing a structured comparison table. The task was renaming a variable f00
TCTestBot Chroniclesintestbot-chronicles.hashnode.dev·Apr 13 · 7 min readBehavioral contract part I : IntroductionSomething happened to me quite a few times in the last weeks : I open Claude Code, start a task, and within thirty seconds it's doing something I never asked for. Last week I wanted to work on a CLI t00
TCTestBot Chroniclesintestbot-chronicles.hashnode.dev·Apr 10 · 12 min readEverything I needed to understand before Playwright tests stopped looking like magicThe first time I opened a properly structured Playwright project, I didn't understand a single line. Not because the code was complicated, but because every line used a concept I'd never seen assemble00
