Loading...
Loading...
Found 53 Skills
Guide for writing tests. Use when adding new functionality, fixing bugs, or when tests are needed. Emphasizes integration tests, real-world fixtures, and regression coverage.
Diagnose and fix failing pytest tests in the pplx-sdk project, following existing test patterns and conventions.
Xcode MCP workflow patterns — BuildFix loop, TestFix loop, preview verification, window targeting, tool gotchas
Implement the minimal code needed to make failing tests pass in the TDD green phase.
Use this skill when writing Playwright tests, implementing visual regression, testing APIs, or automating browser interactions. Triggers on Playwright, page object model, browser automation, visual regression, API testing with Playwright, codegen, trace viewer, and any task requiring Playwright test automation.
Use for test lifecycle hooks: beforeAll, afterAll, beforeEach, afterEach, fixtures, preload.
Plan and build comprehensive Playwright E2E test suites with Page Object Model, authentication state persistence, custom fixtures, visual regression, and CI integration. Uses interview-driven planning to clarify critical user flows, auth strategy, test data approach, and parallelization before writing any tests.
Generate mock data and test fixtures from schemas
Creates test fixtures, mock data, and test scenarios for unit and integration tests. Use when setting up test data, creating mocks, or generating test fixtures.
Iteratively fix test failures until all tests pass. Use when tests are failing and you want Claude to automatically plan and fix them in a loop.
Consult this skill for Python testing implementation and patterns. Use when writing unit tests, setting up test suites, implementing TDD, configuring pytest, creating fixtures, async testing, writing integration tests, mocking dependencies, parameterizing tests, setting up CI/CD testing. Do not use when evaluating test quality - use pensive:test-review instead. DO NOT use when: infrastructure test config - use leyline:pytest-config.
Generate, run, and fix Glubean API tests. Use when the user asks to "write a test", "test this endpoint", "add smoke tests", "explore the API", or work with @glubean/sdk.