Resources
Playbooks, guides, and best practices for AI-native E2E testing.
Best MCP Servers for Claude Code: 10 Worth Installing
A field guide to the best MCP servers for Claude Code, grouped by what they let the agent do: drive a browser, work your repo, pull docs and data, and read production errors. Includes a task-to-server decision table and why installing fewer servers usually works better.
Best QA Wolf Alternatives: Own Your Testing Instead (2026)
QA Wolf is a managed QA service: their engineers plus AI build and maintain your tests. The real alternatives question is whether to outsource testing at all, or make it a capability your team owns. Honest guidance by approach.
What Is Claude Code? The Terminal Agent and Its Extension Model
Claude Code is Anthropic's terminal-based coding agent: it reads your codebase, edits files, runs commands, and connects to external tools over MCP. This hub explains how teams actually run it, how its five extension layers (skills, hooks, subagents, MCP servers, plugins) fit together, and the one thing it cannot see on its own: a real browser.
Claude Code Hooks: Deterministic Rules for an Agentic Workflow
Hooks are code that runs on Claude Code's lifecycle events: before a tool call, after an edit, when a task finishes. Here is the event model, the configuration format, and the recipes worth stealing, including test gates that hold every time.
Claude Code Plugins: The Bundle Layer Explained
Claude Code plugins package skills, subagents, hooks, and MCP server definitions into one versioned, installable unit. This guide covers plugin anatomy, marketplaces, the /plugin command, namespacing, and when a plain skill folder is the better choice.
Claude Code Subagents: How to Define Them and When to Delegate
Claude Code subagents are Markdown files with YAML frontmatter that run delegated tasks in their own context windows. This guide covers the file format, the built-in agent types, how delegation gets triggered, and three working recipes including a browser verification subagent.