Forces strict test-driven development by requiring tests before any implementation code. Won't let you write production code without a failing test first, and actually makes you delete existing code if you wrote it before the test. Walks through the red-green-refactor cycle with mandatory verification steps at each phase. Catches all the common rationalizations like "I'll test after" or "keep it as reference" and shuts them down. Good for breaking the habit of testing after implementation, since it's surprisingly hard to stick to true TDD without external enforcement of the discipline.
A solid Playwright wrapper that handles the annoying parts of local webapp testing. The with_server.py script manages server lifecycle so you don't have to juggle terminals, and it supports multi-server setups like backend plus frontend. The reconnaissance-then-action pattern is smart: wait for networkidle, screenshot the rendered state, identify selectors from what actually loaded, then run your tests. Saves you from the classic mistake of trying to click buttons that haven't rendered yet. The helper scripts are designed as black boxes to keep your context clean, which is thoughtful for complex automation workflows.
This handles the full A/B testing workflow from hypothesis formation to statistical analysis. It walks you through proper test design, calculates sample sizes, helps you avoid the classic "peeking problem" where you stop tests early, and includes frameworks for building ongoing experimentation programs with ICE scoring. The skill catches when you're comparing two approaches and pushes you toward statistical rigor rather than gut decisions. It's particularly strong on the methodology side, with sample size tables and analysis checklists that prevent the common mistakes that make most A/B tests worthless.
A comprehensive reference for Playwright testing that covers everything from basic E2E tests to advanced scenarios like WebSocket testing, mobile emulation, and browser extension testing. The skill is organized by activity rather than feature, so you can quickly find guidance whether you're writing new tests, debugging flaky ones, or implementing complex flows like OAuth popups. It includes specific patterns for Page Object Model, API mocking, accessibility testing with axe-core, and CI/CD optimization. Covers the full spectrum from component testing to security testing, with practical examples for handling authentication, file operations, and multi-tab scenarios.
playwright-cli enables developers to automate browser interactions, navigate web pages, and perform end-to-end testing through a command-line interface powered by Playwright. It solves the problem of manually testing web applications by providing CLI commands for clicking, typing, filling forms, taking screenshots, and managing browser state—allowing QA engineers and developers to script complex user workflows and validate web page behavior programmatically.
The SEO skill optimizes websites for search engine visibility and ranking by providing technical SEO guidance, on-page optimization strategies, and structured data implementation based on Lighthouse audits and Google Search guidelines. It addresses developers and content managers who need to improve crawlability, create XML sitemaps, establish canonical URLs, and configure robots.txt to solve indexing and duplicate content issues. The skill focuses on the ~25% of ranking factors within its scope—technical SEO and on-page optimization—while acknowledging that content quality, backlinks, and Core Web Vitals require complementary efforts.
