Skill UI

Runs automated visual regression tests via Percy, Chromatic, or BackstopJS to capture component or page screenshots, compare them against baselines, and flag unintended UI changes during feature updates or CI/CD runs.

This guide details how to configure robust CI/CD pipelines for Perplexity Sonar API integrations using GitHub Actions. It emphasizes best practices for automated testing, including separating costly live integration tests from lightweight mocked unit tests, ensuring code quality while managing API costs and rate limits.

This skill provides comprehensive guidance on load testing and capacity planning for the Perplexity Sonar API. Users learn how to simulate high traffic volumes, respecting strict rate limits (like 50 RPM), benchmark latency, and estimate operational costs. It is essential for performance engineering, capacity architecture design, or stress testing APIs at scale.

Generates tailored disaster recovery plans and setup code that automate infrastructure configuration, encryption, testing, and multi-region failover for AWS or other environments when you request DR strategy or business continuity support.

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.

Provides a comprehensive workflow for managing feature flags, running A/B/multivariate experiments, and analyzing user cohorts using PostHog. The guide covers implementing flag evaluation both client-side (browser) and server-side (Node.js), and demonstrates how to programmatically set up, track, and query experiment results via API calls (cURL/Bash).

Automates the collection of comprehensive diagnostic evidence for PostHog support tickets. This bundle gathers runtime environment details (Node, Python versions), SDK versions, API connectivity status to US/EU clouds, feature flag settings, event flow testing results, and redacts sensitive environment variables. It provides a structured, support-ready archive for rapid troubleshooting.

This guide provides a comprehensive workflow for setting up a robust local development environment for PostHog integrations. It covers enabling debug mode for real-time event inspection, implementing mocking strategies for stable unit testing, and configuring integration tests using a dedicated development PostHog project. Use this when building or testing analytics tracking features with posthog-js or posthog-node to ensure fast, isolated development cycles.

A comprehensive guide for safely upgrading PostHog SDKs (for JavaScript and Node.js). This resource details critical breaking changes across major versions, such as the explicit requirement for `sendFeatureFlags` in v5.x and the new structured autocapture API for PostHog.js. It provides a structured, step-by-step procedure covering version auditing, code modification, testing, staging validation, and rollback plan.

Blueprint skill describing the architecture, stack, folder layout, API patterns, and testing/deployment workflows used by the Zenith AI customer discovery platform clade. Use it as a reference when working on this dedicated project to understand expectations for frontend, backend, AI integration, and QA.

Guides developers through when and how to apply property-based testing across serializers, validators, normalizers, and smart contracts, highlighting properties, priorities, and workflow steps that complement existing unit testing efforts.

This skill provides guidance and patterns for generating pairwise test cases. Pairwise testing is an advanced testing technique used in software quality assurance (QA) to ensure that every combination of two input parameters is tested. It is highly effective for complex systems with multiple interacting variables, helping developers improve test coverage efficiently while minimizing the overall number of required test cases.