More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Responsive Web UI Audit Agent

    2

    Audits websites and web applications across desktop, tablet, and mobile to detect layout failures, spacing inconsistencies, typography problems, undersized controls, breakpoint defects, overflow, navigation issues, form problems, table failures, sticky-element collisions, accessibility risks, and mobile usability defects.

    $7.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Responsive Web UI Audit Agent

    Responsive Web UI Audit Agent

    Example session with this skill installed

    Project name
    NexaFlow Analytics Platform

    Website or application type
    Multi-tenant B2B SaaS dashboard

    Primary users
    Operations managers
    Analysts
    Team leads
    Administrators

    Primary user tasks
    Review dashboard metrics
    Filter reports
    Inspect customer records
    Export reports
    Update account settings
    Manage team access

    Pages or screens
    Dashboard Home
    Reports
    Customer Directory
    Customer Detail
    Account Settings
    Team Management
    Authentication

    Audit scope
    Full responsive audit with emphasis on mobile usability, breakpoint consistency, data tables, filters, navigation, forms, modals, and sticky actions

    Source material
    Desktop screenshots
    Tablet screenshots
    Mobile screenshots
    Selected Figma exports
    React component files
    Tailwind configuration
    CSS files
    Storybook stories
    Known bug reports

    Current breakpoints
    640 px
    768 px
    1024 px
    1280 px
    Several component-specific arbitrary breakpoints

    Target viewport range
    320 px to 1920 px

    Supported browsers
    Current and previous major versions of Chrome, Safari, Firefox, and Edge

    Supported devices
    Desktop
    Laptop
    Tablet
    Mobile
    Portrait and landscape

    Frontend stack
    Next.js
    React
    TypeScript

    Styling approach
    Tailwind CSS with semantic CSS variables and several legacy CSS modules

    Component library
    Custom components with Radix UI primitives

    Design system
    Partial

    Known issues
    Horizontal scrolling on reports
    Filters overflow on mobile
    Sidebar drawer is difficult to close on short screens
    Settings forms remain two columns too long
    Sticky action bar covers error messages
    Long navigation labels overlap utility controls
    Some mobile inputs trigger browser zoom
    Several modal dialogs exceed viewport height

    Mobile traffic importance
    High

    Accessibility target
    WCAG 2.2 AA implementation review

    Localization
    English
    Spanish planned
    Allow at least 30% text expansion
    Future RTL support

    Need output
    Executive audit
    Detailed issue inventory
    Viewport matrix
    Breakpoint analysis
    Mobile navigation audit
    Form audit
    Table audit
    Overlay audit
    Remediation roadmap
    Acceptance criteria
    Regression tests
    Developer handoff
    Launch-readiness checklist

    Special constraints
    Clearly separate observed defects from inferred root causes.
    Do not claim real-device testing.
    Do not recommend hiding overflow without identifying the source.
    Preserve semantic reading order.
    Include zoom, reflow, content stress, and localization stress.

    • Read your context and instructions
    • Compiled the responsive web ui

    === RESPONSIVE WEB UI AUDIT ===

    Project
    NexaFlow Analytics Platform

    Application Type
    Multi-tenant B2B SaaS dashboard

    Audit Scope
    Dashboard, reports, customer records, account settings, team management, authentication, navigation, filters, data tables, forms, modals, drawers, and sticky actions.

    Evidence Reviewed

    • Desktop screenshots
    • Tablet screenshots
    • Mobile screenshots
    • Selected Figma exports
    • React component files
    • Tailwind configuration
    • CSS modules
    • Storybook stories
    • Known bug reports

    Evidence Limitation
    No live browser, real-device, keyboard, screen-reader, or production-data testing was performed. Findings requiring behavioral confirmation are labeled Requires Live Validation.

    === EXECUTIVE SUMMARY ===

    The desktop application is generally usable, but the responsive implementation compresses several desktop patterns instead of adapting them for smaller widths.

    The highest-impact defects are

    1. The Reports page creates horizontal page scrolling.
    2. The mobile navigation drawer becomes difficult to close on short screens.
    3. The filter toolbar exceeds the viewport between approximately 360 and 480 pixels.
    4. The sticky action bar covers validation errors and pagination.
    5. Data tables lack a deliberate mobile strategy.
    6. Account settings retain a two-column form layout too long.
    7. Several inputs use text sizes that may trigger unwanted browser zoom.
    8. Modals exceed the available viewport height.
    9. Long translated labels are likely to break navigation and toolbar layouts.
    10. Breakpoint behavior is split across framework defaults and arbitrary component values.

    === RESPONSIVE SCORECARD ===

    Layout
    2 / 5 — Weak

    Spacing
    3 / 5 — Adequate

    Typography
    2 / 5 — Weak

    Controls
    3 / 5 — Adequate

    Navigation
    2 / 5 — Weak

    Forms
    2 / 5 — Weak

    Tables And Dense Data
    1 / 5 — Critical

    Media
    4 / 5 — Strong

    Overlays
    2 / 5 — Weak

    Sticky Elements
    1 / 5 — Critical

    Mobile Usability
    2 / 5 — Weak

    Tablet Usability
    3 / 5 — Adequate

    Desktop Scalability
    4 / 5 — Strong

    Zoom And Reflow
    2 / 5 — Weak

    Implementation Consistency
    2 / 5 — Weak

    QA Readiness
    2 / 5 — Weak

    === VIEWPORT MATRIX ===

    Very Narrow
    320–359 px

    Primary Risks

    • Filter overflow
    • Button-label wrapping
    • Mobile header collision
    • Sticky-bar coverage
    • Modal width

    Narrow Mobile
    360–389 px

    Primary Risks

    • Table overflow
    • Navigation label pressure
    • Form error wrapping
    • Input zoom

    Standard Mobile
    390–479 px

    Primary Risks

    • Filter toolbar
    • Dense card layouts
    • Sticky action collisions

    Large Mobile And Small Tablet
    480–767 px

    Primary Risks

    • Inconsistent column transitions
    • Form fields remaining side by side
    • Tablet navigation ambiguity

    Tablet
    768–1023 px

    Primary Risks

    • Sidebar transition
    • Table compression
    • Wrapped toolbar controls

    Small Desktop
    1024–1279 px

    Primary Risks

    • Main content compression beside the sidebar
    • Arbitrary component breakpoints

    Desktop
    1280–1439 px

    Primary Risks

    • Limited

    Wide Desktop
    1440–1919 px

    Primary Risks

    • Excessive line length in selected settings pages
    • Inconsistent maximum content width

    === BREAKPOINT INVENTORY ===

    Breakpoint
    640 px

    Source
    Tailwind default

    Primary Use
    Mobile-to-tablet component changes

    Recommendation
    Keep and document.

    Breakpoint
    768 px

    Source
    Legacy CSS and selected component rules

    Primary Use
    Navigation and form changes

    Conflict
    Overlaps conceptually with the 640 px transition.

    Recommendation
    Audit and consolidate based on content pressure.

    Breakpoint
    1024 px

    Source
    Tailwind default and application shell

    Primary Use
    Sidebar and major grid changes

    Recommendation
    Keep as a shell-level transition.

    Breakpoint
    1280 px

    Source
    Tailwind default

    Primary Use
    Wide content layouts

    Recommendation
    Keep when justified by container design.

    Arbitrary Breakpoints
    700 px, 820 px, 900 px, 1100 px

    Risk
    Component behavior is difficult to predict and maintain.

    Recommendation
    Preserve only breakpoints supported by component-specific content pressure. Remove duplicated or conflicting rules.

    === CRITICAL FINDING 01 ===

    Finding ID
    RWD-001

    Title
    Reports table causes horizontal page scrolling

    Category
    Overflow / Table

    Status
    Observed

    Affected Widths
    320–767 px

    Severity
    Critical

    User Impact
    Users must pan the entire page horizontally to reach columns and row actions. Navigation and page controls move off-screen.

    Business Impact
    Report review and export workflows become unreliable on mobile.

    Likely Cause
    Fixed table minimum width combined with page-level overflow rather than an isolated scroll region.

    Recommended Remediation
    Select an explicit responsive table strategy.

    Recommended Model

    • Desktop: full table
    • Tablet: horizontally scrollable table region with visible scroll affordance and prioritized columns
    • Narrow mobile: summary cards with the primary row action exposed
    • Secondary actions: accessible menu
    • Detail content: dedicated record page or expandable region

    Do Not
    Apply page-level overflow hiding as the primary fix.

    Acceptance Criteria
    Given the viewport is 360 pixels wide,
    when the Reports page renders records with long customer names,
    then the page itself does not scroll horizontally, all material record information remains available, and the primary record action can be reached by keyboard and touch.

    Regression Tests

    • 320 px
    • 360 px
    • 390 px
    • 480 px
    • 767 px
    • 768 px
    • Long customer name
    • Empty table
    • Loading state
    • Error state
    • Selected rows
    • Bulk action toolbar

    Confidence
    High

    Owner
    Frontend and Product Design

    === CRITICAL FINDING 02 ===

    Finding ID
    RWD-002

    Title
    Sticky action bar covers validation errors and pagination

    Category
    Sticky Elements

    Status
    Observed

    Affected Widths
    320–767 px

    Severity
    Critical

    User Impact
    Important form feedback and navigation controls are obscured.

    Likely Cause
    Fixed bottom positioning without reserved content space or safe-area handling.

    Recommended Remediation

    • Reserve document space equal to the sticky element's rendered height.
    • Include bottom safe-area padding.
    • Hide or reposition the bar while a modal, drawer, or mobile keyboard is active.
    • Ensure focused fields and errors scroll above the bar.
    • Test browser zoom and orientation.

    Acceptance Criteria
    Given a validation error appears near the bottom of a mobile form,
    when focus moves to the invalid field,
    then the field and its complete error message remain visible above the sticky action bar.

    Confidence
    High

    Owner
    Frontend

    === HIGH FINDING 03 ===

    Finding ID
    RWD-003

    Title
    Mobile filter toolbar exceeds the viewport

    Category
    Controls / Overflow

    Status
    Observed

    Affected Widths
    360–480 px

    Severity
    High

    User Impact
    Some filters and the clear action become inaccessible.

    Likely Cause
    No wrapping strategy, no overflow container, and several fixed-width controls.

    Recommended Remediation

    • Keep one primary filter visible.
    • Move secondary filters into an accessible filter drawer.
    • Show the active-filter count.
    • Preserve applied values.
    • Keep Clear Filters available.
    • Avoid nested horizontal scrolling.

    Acceptance Criteria
    Given the viewport is 360 pixels wide and five filters are available,
    when the page loads,
    then the page remains within the viewport, one primary filter remains directly accessible, and all secondary filters can be opened through a clearly labeled control.

    Confidence
    High

    Owner
    Design and Frontend

    === HIGH FINDING 04 ===

    Finding ID
    RWD-004

    Title
    Navigation drawer is not reliable on short mobile screens

    Category
    Navigation / Overlay

    Status
    Observed

    Affected Conditions
    Mobile width with short viewport height

    Severity
    High

    User Impact
    The close control and lower navigation items can become difficult to reach.

    Recommended Remediation

    • Use a full-height drawer constrained to the dynamic viewport.
    • Keep the drawer header and close control visible.
    • Make navigation content independently scrollable.
    • Respect safe areas.
    • Move focus into the drawer.
    • Prevent background keyboard interaction.
    • Close on Escape.
    • Restore focus to the trigger.

    Acceptance Criteria
    Given a viewport of 390 by 600 pixels,
    when the mobile menu opens,
    then the close control remains visible, all navigation items are reachable through internal scrolling, background content cannot receive keyboard focus, and focus returns to the menu trigger after closing.

    Confidence
    High

    Owner
    Frontend

    === HIGH FINDING 05 ===

    Finding ID
    RWD-005

    Title
    Account settings form remains two columns at insufficient widths

    Category
    Forms / Layout

    Status
    Observed

    Affected Widths
    640–900 px

    Severity
    High

    User Impact
    Labels, inputs, helper text, and errors become compressed.

    Recommended Remediation
    Collapse to one column when the minimum usable field width cannot be preserved. Determine the transition based on form content rather than a generic device label.

    Acceptance Criteria
    Given the longest approved field label and error message,
    when the settings form is displayed below the approved two-column minimum width,
    then fields stack into one column without clipping, overlapping, or horizontal scrolling.

    Confidence
    High

    Owner
    Design and Frontend

    === TYPOGRAPHY AUDIT ===

    Observed Issues

    • Some input text appears undersized on mobile.
    • Long page titles create awkward two- and three-line wraps.
    • Table text is reduced excessively to preserve columns.
    • Helper text becomes difficult to read.
    • Wide desktop settings descriptions exceed comfortable line length.

    Recommendations

    • Define responsive typography tokens.
    • Set a readable minimum input text size.
    • Avoid shrinking table text to solve width problems.
    • Constrain long-form text width.
    • Test headings with translated text.
    • Define line-clamp behavior only when full-text access is available.

    === CONTROL AND TOUCH AUDIT ===

    Observed Risks

    • Mobile header icon targets appear smaller than their interactive need.
    • Pagination controls are placed too closely.
    • Table row actions use small icon-only controls.
    • Carousel arrows are close to the viewport edge.

    Recommendations

    • Increase interactive target dimensions independently of visible icon size.
    • Add separation between adjacent controls.
    • Provide accessible names for icon-only actions.
    • Verify focus visibility.
    • Test accidental activation risk on mobile.

    === FORM AUDIT ===

    Issues

    • Two-column layouts persist too long.
    • Long validation errors break the grid.
    • Sticky actions cover lower fields.
    • Input text may trigger mobile zoom.
    • Modal forms do not adapt to the mobile keyboard.

    Recommended Rules

    • Stack fields according to minimum usable content width.
    • Preserve entered values after errors.
    • Associate error messages programmatically.
    • Move focus to the first invalid field.
    • Keep focused fields visible above the keyboard and sticky controls.
    • Use appropriate mobile input types and autocomplete values.

    === TABLE AUDIT ===

    Current Problem
    Desktop table behavior is preserved at mobile widths.

    Recommended Strategies

    Customer Directory
    Card transformation on narrow mobile.

    Reports
    Scrollable table region on tablet and summary cards on narrow mobile.

    Team Management
    Priority columns plus row action menu.

    Audit Log
    Horizontal table scroll with timestamp and action columns prioritized.

    Do not use one responsive strategy for every table.

    === MODAL AND DRAWER AUDIT ===

    Observed Issues

    • Selected modals use fixed heights.
    • Footer actions can leave the visible viewport.
    • Drawers do not always scroll independently.
    • Mobile keyboard behavior is undocumented.

    Recommended Rules

    • Constrain overlays to the dynamic viewport.
    • Allow internal content scrolling.
    • Keep actions reachable.
    • Preserve focus management.
    • Define Escape behavior.
    • Restore focus after closing.
    • Test with short heights, zoom, and mobile keyboard.

    === ZOOM AND REFLOW AUDIT ===

    Requires Live Validation

    • 125% browser zoom
    • 150% browser zoom
    • 200% browser zoom
    • Text enlargement
    • Narrow reflow behavior

    Priority Areas

    • Sticky actions
    • Modal dialogs
    • Navigation
    • Tables
    • Settings forms
    • Long page headers
    • Filter controls

    Acceptance Criterion
    Given browser zoom is increased to 200%,
    when the Dashboard and Settings pages are reviewed,
    then primary content and controls remain available without two-dimensional page scrolling except where a deliberately scrollable data region is required.

    === CONTENT STRESS TESTS ===

    Required Test Content

    • 60-character page title
    • 30-character navigation label
    • 40-character button label
    • Long customer name
    • Large currency value
    • Negative percentage
    • Four status badges
    • Long validation error
    • Long URL
    • Spanish translation
    • Future RTL layout sample

    Expected Result
    Components reflow, wrap, truncate with accessible full-text access, or switch layout without overlap or page-level overflow.

    === BREAKPOINT CONSOLIDATION PLAN ===

    1. Inventory all media queries and responsive utilities.
    2. Group them by shell, page template, and component.
    3. Identify duplicate values.
    4. Identify contradictory rules.
    5. Define shell-level transitions.
    6. Define container-level transitions.
    7. Preserve component-specific breakpoints only where content pressure justifies them.
    8. Replace arbitrary one-off values with documented component behavior.
    9. Add Storybook responsive stories.
    10. Add adjacent-width regression tests.

    === IMPLEMENTATION ROADMAP ===

    Phase 1 — Critical:

    • Remove page-level table overflow.
    • Correct sticky-bar coverage.
    • Repair short-height navigation drawer.
    • Repair mobile filter overflow.

    Phase 2 — High:

    • Collapse settings forms earlier.
    • Correct mobile input sizing.
    • Constrain modals to the viewport.
    • Repair long-label navigation collisions.

    Phase 3 — Medium:

    • Consolidate breakpoint rules.
    • Improve typography scaling.
    • Normalize spacing.
    • Improve tablet transitions.
    • Add content and localization stress tests.

    Phase 4 — QA:

    • Browser testing
    • Device testing
    • Keyboard testing
    • Zoom and reflow
    • Orientation
    • Visual regression
    • Accessibility review

    === REGRESSION TEST MATRIX ===

    Widths

    • 320
    • 360
    • 375
    • 390
    • 430
    • 480
    • 640
    • 767
    • 768
    • 900
    • 1023
    • 1024
    • 1280
    • 1440
    • 1920

    Heights

    • 568
    • 600
    • 667
    • 800
    • 900

    Conditions

    • Portrait
    • Landscape
    • 100% zoom
    • 150% zoom
    • 200% zoom
    • Long content
    • Spanish content
    • Empty state
    • Loading state
    • Error state
    • Permission state
    • Mobile keyboard
    • Sticky bar active
    • Modal open
    • Navigation drawer open

    === LAUNCH-READINESS CHECKLIST ===

    • No page-level horizontal scrolling.
    • Primary navigation works at every target width.
    • Mobile drawer supports focus management.
    • Forms remain readable and operable.
    • Input text does not create unwanted zoom behavior.
    • Tables use an approved responsive strategy.
    • Modals fit the viewport.
    • Drawers scroll internally.
    • Sticky elements do not cover content.
    • Safe areas are respected.
    • Focus remains visible.
    • Zoom and reflow are tested.
    • Long content is tested.
    • Localization expansion is tested.
    • Loading and error states are tested.
    • Adjacent breakpoint widths are tested.
    • Browser and device validation is completed.

    === OPEN QUESTIONS ===

    • Which table fields are essential on mobile?
    • Which filters must remain immediately visible?
    • Is the sticky action bar required on every settings page?
    • Which breakpoint values are official design tokens?
    • Is RTL support part of the current release?
    • Which browsers require formal support?
    • Are mobile landscape workflows important?
    • Are Storybook visual regression tools available?
    • Is the live application available for keyboard and zoom validation?

    === KNOWN LIMITATIONS ===

    • Real-device behavior has not been verified.
    • Browser-specific rendering has not been verified.
    • Keyboard and focus behavior requires live testing.
    • Screen-reader compatibility requires manual validation.
    • Exact CSS root causes may differ from the current hypotheses.
    • Performance impact requires measured data.
    • Accessibility compliance cannot be certified through this audit alone.

    === FINAL AUDIT NOTE ===

    Findings are based on the supplied screenshots, recordings, code excerpts, design files, and written descriptions. Final validation requires browser, device, keyboard, zoom, content, localization, accessibility, and implementation testing.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Responsive Web UI Audit Agent helps web designers, frontend developers, agencies, business owners, SaaS teams, product teams, QA engineers, no-code builders, accessibility reviewers, and design-system teams identify and correct responsive interface defects.

    The skill evaluates websites and web applications across desktop, tablet, mobile, narrow mobile, landscape orientation, short-height screens, wide desktop, browser zoom, text enlargement, long-content conditions, localization expansion, loading states, error states, empty states, and other real-world interface pressures.

    It audits page layouts, containers, grids, spacing, typography, line length, content wrapping, button dimensions, touch targets, navigation, menus, forms, tables, charts, images, videos, modals, drawers, popovers, tooltips, sticky headers, fixed footers, mobile CTA bars, cookie banners, chat widgets, horizontal overflow, browser zoom, responsive reflow, visual order, DOM order, and breakpoint consistency.

    The agent can analyze marketing websites, landing pages, SaaS applications, dashboards, admin panels, e-commerce stores, product pages, checkout flows, booking systems, education platforms, CRM interfaces, finance applications, marketplaces, portfolios, service websites, enterprise portals, internal tools, onboarding flows, pricing pages, settings screens, tables, forms, and component libraries.

    It produces executive summaries, viewport matrices, breakpoint inventories, responsive scorecards, issue severity ratings, user-impact explanations, likely root causes, implementation-oriented remediation guidance, developer acceptance criteria, regression tests, launch-readiness checklists, component-specific responsive rules, breakpoint consolidation plans, ownership recommendations, and structured JSON audit results.

    The skill clearly distinguishes observed defects, inferred causes, recommended changes, open questions, and issues requiring live browser or device validation.

    The core commercial promise is: identify responsive UI defects, explain their impact, and convert them into prioritized, testable remediation requirements.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Frontend & Web Apps.

    This skill creates responsive UI audits, defect reports, breakpoint analyses, remediation guidance, acceptance criteria, regression test plans, and developer handoff documentation.

    It does not directly guarantee real-device validation, browser compatibility, accessibility compliance, screen-reader compatibility, visual-regression accuracy, source-code correctness, performance compliance, or production readiness unless the required tools, environments, and permissions are available.

    Screenshot-based analysis cannot reliably reveal DOM order, focus order, keyboard behavior, touch interaction, hover behavior, scroll locking, dynamic viewport behavior, mobile keyboard effects, exact media-query logic, or the precise CSS source of a defect.

    Source-code analysis may still require live validation because runtime data, browser rendering, third-party widgets, dynamic content, and environment-specific styles can change behavior.

    The skill must not claim that a site passed real-device testing, browser testing, keyboard testing, screen-reader testing, zoom testing, or accessibility review unless supporting evidence is available.

    Final validation should include live browser testing, real-device testing, keyboard testing, browser zoom, responsive reflow, orientation changes, content stress, localization stress, accessibility review, performance review, and implementation QA.

    The skill does not guarantee reduced bounce rates, improved conversion, lower mobile abandonment, faster development, fewer bugs, or complete responsive consistency.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 months ago

    Permissions

    Read Files
    Browser
    Write Files

    File Scopes

    *.md
    *.txt
    *.csv
    *.xlsx
    *.json
    *.yaml
    *.yml
    *.html
    *.css
    *.scss
    *.sass
    *.less
    *.js
    *.jsx
    *.ts
    *.tsx
    *.vue
    *.svelte
    *.liquid
    *.php
    *.svg
    README.md
    responsive/**
    audits/**
    screenshots/**
    recordings/**
    figma/**
    design-system/**
    tokens/**
    breakpoints/**
    containers/**
    grids/**
    layouts/**
    spacing/**
    typography/**
    controls/**
    navigation/**
    forms/**
    tables/**
    charts/**
    media/**
    modals/**
    drawers/**
    overlays/**
    sticky/**
    overflow/**
    mobile/**
    tablet/**
    desktop/**
    zoom/**
    reflow/**
    orientation/**
    accessibility/**
    localization/**
    content-stress/**
    storybook/**
    tests/**
    visual-regression/**
    remediation/**
    handoff/**
    acceptance-criteria/**
    qa/**
    risks/**
    templates/**
    docs/**

    This skill uses file access to read user-provided screenshots, viewport-specific images, screen recordings, browser recordings, Figma exports, design specifications, responsive annotations, HTML, CSS, Sass, Less, Tailwind configurations, JavaScript, TypeScript, React components, Next.js components, Vue components, Angular templates, Svelte components, Storybook stories, design tokens, breakpoint definitions, grid specifications, component documentation, browser-support requirements, accessibility requirements, analytics summaries, mobile-abandonment observations, support tickets, bug reports, QA notes, localization examples, long-content examples, form schemas, table schemas, navigation specifications, modal requirements, and platform-theme files. It uses write access to create structured Markdown, text, CSV-style, JSON-style, YAML-style, and implementation-oriented outputs such as responsive UI audits, defect inventories, severity reports, viewport matrices, breakpoint audits, container audits, grid audits, overflow reports, typography reviews, touch-target reviews, navigation audits, form audits, table audits, modal and drawer audits, sticky-element reports, responsive design-system audits, CSS architecture recommendations, remediation roadmaps, acceptance criteria, regression tests, QA checklists, launch-readiness reports, and developer handoff documents. Browser access is useful when the host environment permits live public-page inspection, viewport testing, browser-documentation review, public framework-documentation review, accessibility-standard review, or platform-specific responsive research. The skill should clearly distinguish: Observed: Directly visible in screenshots, recordings, live pages, source files, or supplied documentation. Inferred: A likely cause or responsive risk suggested by the available evidence. Recommended: A proposed remediation intended to improve responsive behavior, usability, accessibility, or implementation quality. Requires Live Validation: A finding that cannot be confirmed without browser, device, keyboard, zoom, interaction, or implementation testing. Open Question: A decision requiring clarification from design, engineering, product, content, QA, or accessibility owners. The default safe setup does not require production credentials, customer data, unrestricted code changes, deployment access, or server administration.

    Listed3 months ago

    What's inside

    Frequently Asked Questions

    The agent simulates various viewport sizes and environmental pressures—such as browser zoom and text enlargement—to identify layout failures like horizontal overflow, overlapping elements, 'sticky' collisions, and touch-target issues that standard automated tools often miss.

    You will receive the AI skill itself, along with a suite of output templates including viewport matrices, responsive scorecards, and implementation-oriented remediation guides to help your team fix identified issues immediately.

    The agent is compatible with most leading AI platforms that support multimodal analysis; simply provide the agent with screenshots or URLs of the interface you wish to audit to start the process.

    Yes, the agent is specifically designed to handle complex SaaS layouts, including dashboards, data-heavy tables, admin panels, and multi-step onboarding flows across all device types.

    The agent produces structured reports that include likely root causes, developer acceptance criteria, and prioritized remediation steps, making it easy to convert audit findings directly into Jira tickets or GitHub issues.

    New in Frontend & Web Apps