b2b-web-policy-auditor

Audit UI designs for Empty/Loading/Error states, responsiveness, and WCAG 2.1 AA accessibility.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/herren-official/product-agents --skill b2b-web-policy-auditor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: b2b-web-policy-auditor
Source: https://github.com/herren-official/product-agents/tree/main/skills/b2b-web/policy-auditor
Command: npx skills add https://github.com/herren-official/product-agents --skill b2b-web-policy-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design policy gaps across UI screens, including Empty/Error/Loading states, responsive behavior, and accessibility, to prevent UX regressions.

Core Features & Use Cases

  • Policy gap detection across screens, including WCAG 2.1 AA accessibility checks.
  • Backlog/design-request generation for missing policies and policy-related fixes.
  • Use Case: In a redesign sprint, run policy-auditor on multiple screens to surface compliance gaps and auto-create backlog items.

Quick Start

Provide a design inventory or exported screens and instruct the auditor to identify policy gaps.

Frequently Asked Questions about b2b-web-policy-auditor

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

FAQPage Schema
How do I audit UI designs for WCAG 2.1 AA accessibility and policy gaps?▼

Audit UI designs for accessibility and policy gaps by providing a design inventory or exported screens to identify missing Empty, Loading, and Error states, responsiveness issues, and WCAG 2.1 AA compliance failures.

Can I automatically generate backlog items for missing UI states and accessibility fixes?▼

You can generate backlog and design-request items for missing policies and accessibility fixes by running an audit on your UI screens to surface compliance gaps and output actionable backlog entries.

What is the best way to check responsiveness and error states across web interfaces?▼

Checking responsiveness and error states across web interfaces involves scanning your exported design screens to detect policy gaps and prevent UX regressions during a redesign sprint.

Do I need a specific design file format to run a UI policy audit?▼

No specific file format is required as a dependency; you simply need to provide a design inventory or exported screens to instruct the auditor to identify UI policy gaps and accessibility issues.

How does a UI policy audit integrate with existing design review workflows?▼

The UI policy audit integrates with design review workflows by identifying compliance gaps and generating outputs that align with backlog and design-request workflows for phase-2 harness processes.

When should I run an accessibility and policy audit during a design sprint?▼

Run an accessibility and policy audit during a redesign sprint to proactively surface UX regressions, missing screen states, and WCAG compliance failures before finalizing the web interface design.