responsive-tester

Automate cross-device UI validation for IronForge platforms across mobile, tablet, desktop, and TV.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Techlemariam/IronForge --skill responsive-tester-techlemariam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: responsive-tester
Source: https://github.com/Techlemariam/IronForge/tree/main/.agent/skills/responsive-tester
Command: npx skills add https://github.com/Techlemariam/IronForge --skill responsive-tester-techlemariam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-device and TV-mode validation for IronForge UI across mobile, tablet, desktop, and television interfaces, ensuring a consistent user experience.

Core Features & Use Cases

  • Viewport Snapshots: capture UI at defined breakpoints to verify layout consistency.
  • Touch Target Audit: ensure targets meet sizing guidelines for touch devices.
  • Focus Management: validate keyboard and remote navigation across platforms.
  • TV Mode Validation: enforce 10-foot UI principles for television interfaces.

Quick Start

Run the responsive-tester workflow to validate the user interface across mobile, tablet, desktop, and TV breakpoints.

Frequently Asked Questions about responsive-tester

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

FAQPage Schema
How do I automate cross-device UI validation for different screen breakpoints?

Automate cross-device UI validation by running a workflow that scans source TSX files for breakpoints and applies viewport testing rules to capture layout consistency across mobile, tablet, desktop, and TV contexts.

What is TV mode validation and how does it enforce 10-foot UI principles?

TV mode validation enforces 10-foot UI principles for television interfaces by verifying that layout patterns, focus states, and navigation conventions in source TSX files meet television display requirements.

How do I audit touch targets to ensure they meet sizing guidelines for mobile and tablet devices?

Audit touch targets by scanning source TSX files for UI patterns and verifying that interactive elements meet sizing guidelines for touch devices across mobile and tablet breakpoints.

Can I validate keyboard and remote navigation focus states across multiple platforms?

Validate keyboard and remote navigation across platforms by applying viewport testing rules that check focus management and focus states in source TSX files for mobile, tablet, desktop, and TV contexts.

Do I need viewport testing rules in frontmatter to perform responsive testing?

Viewport testing rules provided in frontmatter are required, as the responsive testing workflow uses them to scan source TSX files and verify breakpoints, touch targets, focus states, and TV UI conventions.

Why does my responsive testing workflow fail to detect layout inconsistencies across breakpoints?

Responsive testing may miss layout inconsistencies if viewport testing rules in frontmatter are incomplete or if source TSX files lack defined breakpoint patterns for the workflow to scan and validate.