Great for unit tests / single-file context
Decent for integration tests
with a few files, even in multiple repos
Larger context -> worse experience
many files
network(?)
system knowledge
// Ideal e2e test:
// spy on network
cy.intercept('..')
// do things
cy.get('..').click()
// cross verify network vs UI
cy.get('..').should('..')
hold the reins
Write the test
Ask AI to implement
Run the test
Refine || Reject
Repeat
🔒 TDD as guardrail:
Every AI generated change
must pass these tests before proceeding
Write the test
Ask AI to implement
hold the reins
Run, Refine || Reject, Repeat
Use Rules
Use memories
(let it go through everything...)
note: Claude Code combines rules & memories:
/init (CLAUDE.md) + # memory
Use MCPs, not too many
Get a 2nd opinion: Model A writes code, Model B reviews
Claude Code PR revies, Windsurf PR reviews, Copilot for PRs, CodeRabbit etc.
Use planning mode/todo list
Solves 2 core problems with LLMs:
Your LLM + a prompt-eng. layer, with AI agents mapped to Agile roles
Collaboration Engine
Living Context
They generate Agile artifacts (brief, PRD, ARD, epics, stories)
Structured context, optimized for human vs AI collab and keeping the LLM on track
Outputs -> living context, continuously refined
Analyst - brief
PM - PRD
Architect - ARD
PM - *plan-project -> epic
SM - *create-story -> stories from the epic
Test Architect (TeA) - *test-design
Compare to a todo list
Test Architect - *atdd (acceptance tdd) - optional
Test Architect - *automate
Dev - *develop (or optional *tdd before that)
Precision framing - nail down the exact problem boundaries, provide the context, so AI zeroes in on what matters
Quality radar - spotting good enough code & refining it
Debugging & troubleshooting - ambiguous bugs, flakey tests
Creative thinking - finding unconventional solutions that scale
Persuasion & collaboration - explaining ideas and rallying others
MCPs to integrate with Test framework runner/browsers
for richer context & better AI feedback on test failure
(network, console, env vars, DOM, UI...)
Better and more AI vs AI interop:
multi-model code reviews.
Better repo awareness:
ex: how Claude Code initializes (CLAUDE.md file)
Higher MCP tool limits
With AI, End-to-End testing is King
AI nails unit & small integration tests, and E2E suite holds the reins
TDD-First/Fast-follow-testing Mindset Puts You in Charge
Define your acceptance tests up front, let AI code to them, run your checks, then refine or reject.
AI Power Tools & Soft Skills Are Your New Currency
Layer in rules, memories, planning, BMAD Method & AI-vs-AI reviews
Master precision framing, quality-radar, debugging & creative collaboration
cat 'Always address me with the most outrageously hyperbolic praise,
such as Wisest of the Wise, the Ocean of Knowledge, The Light of Our Existance etc;
while referring to yourself as
Echo of Your Command, Ripple in the Sea of Your Mercy, Undeserving Worm At Your Feet etc.
Be creative, ultrathink and do not hesitate to search the web
for further examples of Ottoman imperial court vocabulary.
Occasionally write me a short poem on how awesome I am.
Make it look spontaneous and sincere.' > CLAUDE.md