Unit Testing

Conventional Commits specification format. Use when creating commit messages. Format: <type>(<scope>): <description>. Types: feat, fix, chore, docs, test, refactor, style, perf. CRITICAL: All commits must follow conventional commit format.

Expert-level SolidJS and SolidStart development skill with 20+ years senior/lead engineer mindset. Comprehensive guidance for building production-ready, scalable web applications with fine-grained reactivity. Use when Claude needs to: (1) Create new SolidJS/SolidStart projects, (2) Implement TanStack Query/Router/Table/Form integration, (3) Build reactive components with signals/stores/resources, (4) Handle SSR/SSG/streaming with SolidStart, (5) Implement authentication and API routes, (6) Optimize bundle size and performance, (7) Debug reactivity issues and memory leaks, (8) Structure large-scale applications, (9) Implement type-safe patterns with TypeScript, (10) Handle error boundaries and suspense, (11) Build accessible UI components, (12) Deploy to Vercel/Netlify/Cloudflare. Triggers: "solid", "solidjs", "solidstart", "createSignal", "createStore", "createResource", "tanstack solid", "vinxi", "fine-grained reactivity".

Production-ready release workflow examples with signed releases, SLSA provenance, artifact attestations, and minimal permissions.

Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling

Write minimal, strategic tests focused on core user flows and critical paths during feature development, deferring comprehensive edge case testing. Use this skill when writing unit tests, integration tests, or end-to-end tests, creating test files (*.test.ts, *.spec.js, __tests__/*), testing critical user workflows, focusing on behavior rather than implementation details, using descriptive test names, mocking external dependencies (databases, APIs, file systems), ensuring tests run quickly, testing business-critical functionality, or determining which tests to write during development versus dedicated testing phases. Apply this skill when completing features at logical milestones, writing tests for primary user flows, or balancing feature development speed with adequate test coverage.

Verify and test Angular 18 frontend changes using Chrome DevTools MCP. Automatically check console errors, network requests, and visual rendering after implementing tasks or when fixing UI bugs. Use when creating components, debugging visual issues, validating API integration, or ensuring UI requirements are met. File types: .ts, .html, .css, .scss

Generate comprehensive pull request descriptions with summaries and test plans. Use when creating PR descriptions or documenting code changes.

Generate GitHub Actions workflow YAML files for CI/CD pipelines including testing, building, and deployment automation. Triggers on "create GitHub Actions workflow", "generate CI/CD pipeline", "GitHub workflow for", "actions yaml for".

Эксперт по a11y тестированию. Используй для axe-core, automated testing и accessibility audits.

Apply Single Responsibility Principle when writing code. Keep modules focused, cohesive, and loosely coupled. Guide splitting classes with too many methods. Ensure code is reusable and testable.

Comprehensive testing workflows for Practice Hub including Vitest configuration, tRPC router testing, multi-tenant validation, Better Auth flows, and component testing. Use for writing tests, validating multi-tenant isolation, and ensuring production readiness.

Vue 3 and Nuxt 3 development with TDD workflow, QA gates, and E2E test generation. Enforces unit testing before implementation, generates Playwright E2E tests from Gherkin acceptance criteria, and produces JSON reports.

Top username lists for enumeration: common usernames, default credentials, names. Curated essentials for authorized testing.

Generate comprehensive Pest test suites for Laravel projects including tests for controllers, services, Livewire components, commands, jobs, and models with proper describe blocks for organization, mocking setup, happy path and failure scenarios, RefreshDatabase trait, and coverage for all public methods. Use this skill when creating test files for new features, adding test coverage for controllers or services, writing tests for API endpoints, testing Livewire components, ensuring proper test structure with beforeEach and describe blocks, implementing mocking strategies, or writing dataset-driven tests. This skill applies when working on files in tests/Feature/ or tests/Unit/ directories, creating Pest test files, or ensuring comprehensive test coverage.

Guide through RED phase - writing failing tests and verifying failures

Modern Rust backend with Axum, SQLx, tokio + CI/CD automation.Use when: building Rust APIs, high-performance services, or needing build/test/lint/audit automation.Triggers: "axum", "rust backend", "rust api", "sqlx", "tokio", "cargo build","cargo test", "clippy", "rustfmt", "cargo-audit", "cross-compile", "rust ci","release build", "rust security", "shuttle", "actix".

Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.

Designs and documents control testing procedures. Creates test plans, executes walkthroughs, and documents results for audit workpapers.

Find the most recently downloaded Fidelity and Tastytrade portfolio CSV files from Downloads directory. Use when you need to locate the latest portfolio data files before analysis or processing.

Interactive browser automation via Chrome DevTools Protocol. Use when you need to interact with web pages, test frontends, or when user interaction with a visible browser is required.