Standardizes visual audits, responsive design, and behavioral testing for web apps. Use to verify a web UI fix or cross-browser behavior; defer backend API refactors, Playwright installation/tooling setup, and Appium/mobile automation.
npx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill common-web-visual-testing
> [!IMPORTANT]
> Tier 2 (Methodology): Strategy web UI/UX audit.
> Tier 3 (Domain): Responsive, A11y (WCAG), Browser Engine quirk.
Visual test best as Comparative Audit loop:
snapshot --aria + screenshot prod/main.Responses must label the two captures as Before and After (or Baseline and Fixed) and include the diff and neighboring-element side-effect check.
| Change Type | Scenarios to Run |
| :---------------- | :------------------------------------------------- |
| CSS/Layout | Responsive Audit + Hover + CLS Check |
| Forms/Input | Validation Msg + Focus State + Error Boundary |
| Navigation | URL Sync + Sticky Header + Back-Button Persistence |
| Assets/Fonts | Lazy Load + Icon Check + LCP Audit |
| Accessibility | Tab Order + Aria-Snapshot + Color Contrast |
--mask or JS (opacity: 0). Avoid "False Regression".playwright-cli snapshot --aria verify state before done.Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when implementing any feature or bugfix, before writing implementation code
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.
This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
Take hoangnguyen0403/common-web-visual-testing from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.