option-chain-layout-regression

Reproduces and validates Option Chain bottom layout visual stability via manual-first checklist.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/tombelial666/test --skill option-chain-layout-regression
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: option-chain-layout-regression
Source: https://github.com/tombelial666/test/tree/main/.cursor/skills/option-chain-layout-regression
Command: npx skills add https://github.com/tombelial666/test --skill option-chain-layout-regression

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Option Chain bottom layout regression can be visually unstable after frontend changes; this Skill provides a stable manual-first checklist to reproduce the issue and collect evidence for validation.

Core Features & Use Cases

  • Manual-first UI regression workflow for Option Chain bottom layout
  • Captures expected vs actual UI evidence to support validation and debugging
  • Prepares automation hooks for future test automation and integration
  • Supports configurable inputs (BASE URL and symbol), optional browser, screenshot directory, and backlog tracking for traceability

Quick Start

Follow the manual checklist at aiqa/tasks/bug-etnatrader-option-chain-bottom-layout/bug-description.md to begin.

Frequently Asked Questions about option-chain-layout-regression

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform manual UI regression testing for an Option Chain layout?

You perform Option Chain layout regression via a structured manual-first checklist that reproduces visual instability and captures expected vs actual UI evidence for validation during frontend regression cycles.

What environment variables do I need to set up for Option Chain regression checks?

Option Chain regression checks require OPTION_CHAIN_BASE_URL and OPTION_CHAIN_SYMBOL to run. You can optionally configure OPTION_CHAIN_BROWSER and OPTION_CHAIN_SCREENSHOT_DIR to capture evidence across environments.

When should I use a manual checklist over automated UI regression testing?

A manual checklist suits UI regression testing after layout fixes or during release smoke tests where visual stability needs validation. It records evidence to prepare future automation hooks.

How do I collect evidence for Option Chain layout visual instability?

Collect evidence for Option Chain layout visual instability by following the manual checklist to capture screenshots and compare expected vs actual UI states. Use OPTION_CHAIN_SCREENSHOT_DIR to store evidence for validation and debugging.

Can I configure the browser used for Option Chain frontend testing?

Yes, Option Chain frontend testing supports an optional OPTION_CHAIN_BROWSER variable for configurable browser selection. This allows you to confirm layout consistency across different browser environments.