test-ids
WHAT: Test ID constants with hierarchical naming for React Native automated testing. WHEN: unit tests with Testing Library, E2E tests with Maestro, testing interactive elements. KEYWORDS: testID, TEST_IDS, cons...
Explore AI skills for development, content, data and productivity. Compare the description and repository popularity before opening a skill.
WHAT: Test ID constants with hierarchical naming for React Native automated testing. WHEN: unit tests with Testing Library, E2E tests with Maestro, testing interactive elements. KEYWORDS: testID, TEST_IDS, cons...
WHAT: Constants organization with naming conventions and type-safe as const assertions. WHEN: defining test IDs, animation durations, query keys, feature flags. KEYWORDS: constants, SCREAMING_SNAKE_CASE, Pascal...
Runs unit and E2E tests for API, analyzes failures, identifies flaky tests, checks coverage, and suggests fixes
Web application testing principles. E2E, Playwright, deep audit strategies.
Run appropriate tests based on changes using node:test, Testcontainers, and Playwright
Work on a kspec task with proper lifecycle - verify, start, note, submit, PR, complete.
E2E multiplayer testing using Playwright API with multi-client browser contexts. Validates server-authoritative patterns, state synchronization, and anti-cheat measures. Use when testing multiplayer features.
Generate unit tests using Jest with mocking, AAA pattern (Arrange-Act-Assert), and 80%+ coverage target. Use when testing business logic, handlers, or services in isolation.
WHAT: Test ID patterns with data-testid attribute for web testing. WHEN: E2E with Playwright/Cypress, component tests with Testing Library, targeting specific elements. KEYWORDS: data-testid, test ID, getByTest...
Generate integration tests for CQRS handlers with mocked dependencies and co-located fixtures using Jest. Use when testing handlers, database operations, or event publishing in isolation.
WHAT: Jest and @testing-library/react patterns for web component testing. WHEN: testing components with providers, user interactions, async content, form validation. KEYWORDS: testing-library, Jest, screen, use...
E2E test creation and execution for QA. Validates implementations using Playwright API tests that become persistent artifacts for regression.
Guidelines for running and writing unit and E2E tests. Use this when asked to run tests, write tests, debug test failures, or verify code changes. Also use this before performing any merge commands or pushing c...
TypeScript, lint, test, and build validation before committing
Review code changes for bugs, logic errors, regressions, and missing tests. Use when the user asks for a code review, review of uncommitted files, or review of specific diffs/files/PR changes. Default to uncomm...
Migrate JavaScript/TypeScript projects from Biome to oxlint + oxfmt with Prettier fallback. Use when user asks to "migrate to oxlint", "switch from biome to oxc", "use oxfmt", or wants to adopt the oxc toolchai...
Performs comprehensive code review with stack detection, deep logic tracing, and double-verification of bugs before reporting
Run comprehensive quality checks including Pint formatting, PHPStan analysis, and Pest tests. Use this before commits, after major changes, or when requested by user.
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Generate authentication and authorization guards (JWT, API key, roles, permissions) with tenant context validation. Use when protecting API endpoints or implementing RBAC.
This skill should be used when the user asks to "validate external URLs", "check for link rot", "screenshot URLs", "archive external links", or wants to verify and document external web resources (http/https) r...
Bug report format and documentation for failed validations
Diagnose and fix bugs, errors, and unexpected behavior in the codebase
This skill should be used when the user asks to "check internal links", "validate relative paths", "find broken file references", "audit documentation links", or wants to ensure all relative paths and anchors i...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.