AGENT SKILL

ui-accessibility-engineer

Enforces mobile-first Tailwind CSS and strict WCAG 2.1 AA compliance for user-facing UI. Use when building UI components — utility classes only (no custom CSS or inline `style={{}}`), mobile-first breakpoints, visible focus states, alt text, and 4.5:1 contrast.

License 许可
MIT
最近更新
2026-05-27
Stars
★ 0
Forks
0

01 前言 Front Matter

name
ui-accessibility-engineer
vendor
tailwind
description
Enforces mobile-first Tailwind CSS and strict WCAG 2.1 AA compliance for user-facing UI. Use when building UI components — utility classes only (no custom CSS or inline `style={{}}`), mobile-first breakpoints, visible focus states, alt text, and 4.5:1 contrast.

03 SKILL.md 正文

UI/UX Accessibility & Styling Engineer

Policy Capsule

  • Style only with Tailwind utility classes; never write custom CSS files or inline style={{}} objects in components.
  • Follow mobile-first responsive design: default classes target mobile, md: / lg: prefixes scale up.
  • Give every interactive element a visible focus state (focus:ring, focus-visible:*).
  • Provide meaningful alt text on every image; empty alt="" only for purely decorative imagery.
  • Meet WCAG 2.1 AA contrast: minimum 4.5:1 for normal text, 3:1 for large text.
  • Ensure every interactive element is reachable and triggerable via keyboard alone.
  • Use semantic HTML elements (<button>, <nav>, <main>) before reaching for ARIA roles.

Description: Enforces mobile-first Tailwind CSS and strict WCAG AA compliance.

Instruction: You are building user-facing interfaces.

  • Strictly use Tailwind CSS utility classes. DO NOT write custom CSS or inline style={{}} objects.
  • Follow a mobile-first approach: default classes apply to mobile, using md: and lg: prefixes for larger viewports.
  • Enforce WCAG 2.1 AA accessibility: All interactive elements must have focus states (focus:ring), images must have meaningful alt text, and color contrasts must meet the 4.5:1 ratio.

04 同仓库更多 Skills

chrisbarrantes
chrisbarrantes/mandrel

no-capsule-skill

Fixture without a Policy Capsule section.

★ 0
chrisbarrantes
chrisbarrantes/mandrel

backend-security-patterns

Combined backend protocols for authentication (Clerk JWT verification) and PII-safe observability. Use when handling auth on the server, verifying Clerk webhooks via `svix`, scoping metadata via `publicMetadata`/ `privateMetadata`, or sanitizing logs to keep emails, tokens, and request bodies out of telemetry.

★ 0
chrisbarrantes
chrisbarrantes/mandrel

vitest

Writes fast, isolated unit and integration tests with Vitest. Use when each test must run on file-save without shared state — `vi.mock()` for external deps, `vi.spyOn()` for call monitoring, AAA structure, and edge-case coverage for null/undefined/boundary inputs.

★ 0
chrisbarrantes
chrisbarrantes/mandrel

playwright

Robust E2E browser testing with Playwright. Use when writing browser-driven tests — leverage auto-waiting (no `waitForTimeout`), prefer user-visible locators (`getByRole`, `getByText`, `getByLabel`) over CSS/XPath, reuse `storageState` for auth, and enable trace-on-first-retry for CI debugging.

★ 0
chrisbarrantes
chrisbarrantes/mandrel

playwright-bdd

Wires Gherkin `.feature` files to Playwright via the `playwright-bdd` library. Use when running BDD scenarios on a Playwright runtime — pairs with the `gherkin-authoring` skill (scenario prose) and the `playwright` skill (browser conventions). Drives execution by tag expression with trace-first debugging and Playwright-native sharding.

★ 0
chrisbarrantes
chrisbarrantes/mandrel

lighthouse-baseline

Codifies the capture-and-check baseline pattern for long-running quality signals (Lighthouse scores, bundle size, p95 latency, runtime memory). Use when wiring a new metric that needs a baseline file, paired :capture / :check npm scripts, a tolerance-bounded gate, and a weekly refresh cadence — the goal is a hard CI signal that ratchets only with intent.

★ 0