Plan and report accessibility QA for a web or app experience against WCAG 2.2 level AA. Defines scope and a page and flow sample, combines automated scans with manual keyboard, screen reader, zoom and reflow, contrast, semantics, and form-error testing, computes contrast ratios, logs each issue with the success criterion, affected users, severity, and a fix direction, and ends with retest criteria. Use when someone asks for accessibility testing, an accessibility audit plan or report, keyboard or screen reader checks, contrast checks, or WCAG review of a page or flow. Do not use for the overall test plan (use test-plan), the release verdict (use release-regression-report), visual design critique (use design-audit), or posting issue text (use jira-evidence-uploader).
Runs accessibility QA planning and reporting across keyboard, screen reader, contrast, semantics, and forms.
Build enterprise SaaS application surfaces — data tables, list views, dashboards, settings, admin panels, detail/inspector panels, multi-step flows, command palettes — that read as designed rather than assembled. Use when building or redesigning any in-app product surface, CRUD screen, internal tool or admin UI; when a table needs columns, sorting, filters, bulk actions, pagination or empty states; when a form needs validation timing, progressive disclosure or a destructive-action pattern; when an app screen feels cluttered, cramped, "too much chrome", inconsistent, or like a marketing page wearing an app costume. A capability catalog of grounded UX/UI decision rules with real numbers — chrome budget, app type scale, 4px spacing, control tiers and hit targets, table anatomy, product-UI motion, WCAG 2.2 AA — plus drop-in React + Tailwind v4 reference implementations. Do not use for marketing pages, landing pages, or visual-style exploration.
Build enterprise SaaS application surfaces — data tables, list views, dashboards, settings, admin panels, detail/inspector panels, multi-step flows, command palettes — that read as designed rather than assembled. Use when building or redesigning any in-app product surface, CRUD screen, internal tool or admin UI; when a table needs columns, sorting, filters, bulk actions, pagination or empty states; when a form needs validation timing, progressive disclosure or a destructive-action pattern; when an app screen feels cluttered, cramped, "too much chrome", inconsistent, or like a marketing page wearing an app costume. A capability catalog of grounded UX/UI decision rules with real numbers — chrome budget, app type scale, 4px spacing, control tiers and hit targets, table anatomy, product-UI motion, WCAG 2.2 AA — plus drop-in React + Tailwind v4 reference implementations. Do not use for marketing pages, landing pages, or visual-style exploration.
Turn one approved source, such as a research report, webinar, workshop, annual report, or article, into channel-native assets (newsletter section, social posts per platform, blog post, talking points, slide, email, partner kit) without drifting from what the source says. Builds a source claim register so every claim traces to the source, keeps each statistic with its source, base, and date, sets reading level per audience, adds alt text and captions, and classifies every adaptation as Format only, Wording change, or New claim or audience so staff know how much review it needs. Use when asked to repurpose, adapt, cut down, reuse, or turn an approved report or webinar into posts, emails, talking points, or a partner toolkit. Do not use for writing new content from scratch, a single LinkedIn post from an idea (linkedin-post-from-idea), or drafting a whole newsletter issue (newsletter-issue-draft).
Turn one approved source, such as a research report, webinar, workshop, annual report, or article, into channel-native assets (newsletter section, social posts per platform, blog post, talking points, slide, email, partner kit) without drifting from what the source says. Builds a source claim register so every claim traces to the source, keeps each statistic with its source, base, and date, sets reading level per audience, adds alt text and captions, and classifies every adaptation as Format only, Wording change, or New claim or audience so staff know how much review it needs. Use when asked to repurpose, adapt, cut down, reuse, or turn an approved report or webinar into posts, emails, talking points, or a partner toolkit. Do not use for writing new content from scratch, a single LinkedIn post from an idea (linkedin-post-from-idea), or drafting a whole newsletter issue (newsletter-issue-draft).
Review exact image, video, sequence, and campaign asset versions against their brief, brand, continuity, accessibility, and delivery requirements. Use before creative export or approval; do not use as a substitute for human brand, legal, or client acceptance.
Review exact image, video, sequence, and campaign asset versions against their brief, brand, continuity, accessibility, and delivery requirements. Use before creative export or approval; do not use as a substitute for human brand, legal, or client acceptance.
Audit an existing UI against its own job and produce an evidence-backed, ranked findings report. Scopes the audit to named tasks and screens, runs a task walk, then checks visual hierarchy, layout and spacing, accessibility against WCAG 2.2 criteria, information density, cross-screen consistency, and conversion or workflow fit; separates defects from judgment calls; scores each finding by severity, reach, confidence, and effort. Use when someone asks for a design audit, UI review, UX heuristic review, an accessibility and consistency check of screens, or why an interface feels cluttered, confusing, or underperforms. Do not use for redesign directions (use explore-visual-directions), a funnel numbers diagnosis (use diagnose-conversion-funnel), a full site restructure (use map-site-for-redesign), or an accessibility test pass on built software (use accessibility-qa).
Rewrite or review general-audience writing so it is clear, direct, and easy to understand without removing necessary precision.
Rewrite or review general-audience writing so it is clear, direct, and easy to understand without removing necessary precision.
Create a reviewable visual-style exploration for an existing product, page, or interface before implementation. Use when someone asks to see how a current experience would look in a named aesthetic or described vibe, such as glassmorphism, editorial, brutalist, retro, premium, playful, or futuristic. Produces an isolated preview or implementation-ready visual specification without replacing the established brand system or changing production.
Create a reviewable visual-style exploration for an existing product, page, or interface before implementation. Use when someone asks to see how a current experience would look in a named aesthetic or described vibe, such as glassmorphism, editorial, brutalist, retro, premium, playful, or futuristic. Produces an isolated preview or implementation-ready visual specification without replacing the established brand system or changing production.
Audit a web app against WCAG 2.2 level AA before launch and hand back fixes developers can ship. Use when you need automated axe-core scans of key pages and states, a manual keyboard, focus, screen reader, zoom and reflow review, colour contrast checks, accessible forms and error messages, each failure mapped to its WCAG success criterion with a code fix, and a re-test that proves the fix.
Audit a web app against WCAG 2.2 level AA before launch and hand back fixes developers can ship. Use when you need automated axe-core scans of key pages and states, a manual keyboard, focus, screen reader, zoom and reflow review, colour contrast checks, accessible forms and error messages, each failure mapped to its WCAG success criterion with a code fix, and a re-test that proves the fix.