Skill UI

This comprehensive guide details how to configure robust CI/CD pipelines for applications secured by Clerk authentication. It covers setting up GitHub Actions workflows, utilizing Playwright for end-to-end (E2E) testing, managing test user states, and scripting user seeding for reliable automated testing environments. Essential for developers integrating Clerk into their build and deployment process.

A comprehensive guide for mastering major dependency version upgrades in software development. This skill covers compatibility analysis, implementing staged upgrade strategies, resolving dependency conflicts, and setting up robust testing matrices (Unit, Integration, E2E) to ensure a smooth and reliable modernization process for any codebase.

A comprehensive, end-to-end workflow bundle guiding developers through the entire software development lifecycle. It covers project scaffolding, frontend development (React/Next.js), robust backend architecture, database design, rigorous testing (TDD, E2E), code quality review, and modern CI/CD deployment practices for web and mobile applications.

A Playwright-powered guide that bundles organized test suites, Page Object Models, CI/CD workflows, artifact capture, and strategies for stabilizing flaky scenarios so teams ship reliable end-to-end coverage.

This skill provides comprehensive guidance on building reliable, fast, and maintainable end-to-end (E2E) test suites. It ensures code quality by validating critical user journeys and catching regressions in complex workflows before deployment. Essential for setting up robust CI/CD pipelines, cross-browser compatibility, and establishing rigorous QA standards.

A specialist skill for writing robust, maintainable, and scalable End-to-End (E2E) tests using Playwright. This guide covers setting up test infrastructure, implementing Page Object Model (POM), using role-based selectors, handling API mocking, and debugging flaky tests. Ideal for integrating quality checks into CI/CD pipelines and performing complex browser automation.

This comprehensive workflow guides the development of modern, scalable full-stack applications using Next.js 14+, React, and TypeScript. It covers all phases, from project setup and component architecture to advanced data fetching (Server Components, React Query), styling with Tailwind CSS, robust testing (E2E via Playwright), and deployment optimization. Ideal for building complex, production-grade web interfaces.

Provides a comprehensive guide and framework for executing end-to-end (E2E) tests. It simulates real user interactions across the entire application stack, covering browser UI, API calls, and database operations. The guide details best practices like implementing the Page Object Model (POM), configuring multi-browser environments (Playwright, Cypress, Selenium), and establishing robust error handling mechanisms to ensure high application stability and quality.

Generates Jest/RTL unit tests, analyzes Istanbul coverage, scaffolds Playwright E2E suites, and configures fixtures and mocks to boost React/Next.js QA workflows.

This skill simulates a complete, multi-agent software development lifecycle following the principles of Agile and Scrum. It guides the project through six distinct, iterative phases: Architectural Planning, Parallel Implementation, Comprehensive Testing (Unit/E2E), Review, and Finalization. The process uses a convergent diffusion model, refining specifications and resolving conflicts across multiple specialized agents until the project converges and is deemed complete.

A specialized skill designed to ensure robust software quality by covering the entire testing lifecycle. This includes defining test strategies, writing unit, integration, and E2E tests, and implementing advanced testing types like performance (k6), security (OWASP), and functional testing. It guides users through coverage analysis, debugging flaky tests, and generating detailed defect and quality reports.

Validates Claude Code plugin activation by reading files, executing commands, and ensuring trigger phrases and tool permissions work as expected during E2E testing scenarios.