Jordan’s Toolkit
GitHub
← All roles

SPECIALIST PRESET · REVIEW · V0.1.0

QA & Accessibility Reviewer

Verify behavior, keyboard journeys and interface failures using reproducible evidence rather than appearance alone.

Guidance, not a worker. This experimental preset selects skills. It does not launch an agent, establish expertise or grant permissions. Requested mode: read-only; the host must enforce the actual policy.
Inspect the role selection

From a full checkout. JSON includes file hashes, not an installation or an execution.

node tools/bundle.mjs role qa-accessibility-reviewer
Read role registry ↗

Expected handoff

  • Reproduction steps and requirement-linked findings
  • Test coverage, viewport scope and uninspected behavior

Bring this context

  • Target user journeys and candidate build
  • Approved browser and test fixtures

Keep out of scope

  • Do not claim full accessibility certification from automation
  • Do not change source during read-only review

Choose the procedure the task needs.

These 6 skills are references, not instructions to load everything at once.

Original

Behavior Test Design

Turn a feature or bug contract into focused tests with explicit input partitions, observable outcomes, boundary cases, and evidence that the tests detect the behavior they are meant to protect.

Testingexperimental
Original

Interface Quality Review

Review a rendered web interaction for usability, responsive layout, keyboard behavior, state handling, and implementation defects, producing reproducible findings rather than a generic design checklist.

Frontendexperimental
Original

Frontend Accessibility

Implement and verify accessible frontend interactions through native semantics, meaningful names, keyboard/focus behavior and explicit assistive-technology limits.

Accessibilityexperimental
Original

Visual Regression and UI Verification

Use reproducible visual evidence to detect frontend regressions while preserving independent interaction, accessibility and content checks.

Testingexperimental
Original

Frontend Testing Strategy

Choose unit, component and browser checks around user-visible frontend contracts, with independent network fixtures and explicit integration coverage.

Testingexperimental
Original

Affected Verification

Select relevant project-owned checks for an observed change and produce an evidence-based verification report that distinguishes passed, failed, skipped, blocked, and not-run checks.

Verificationexperimental

A private binding, not a fork.

The execution environment supplies real roots, contracts, account context, budgets, tool access and independent acceptance. Keep those private. Review or analysis mode does not itself block a shell command; the host must do that.

Explore Specialist Role Composition →