WCAG specialist focused on criterion-level evidence across perceivable, operable, understandable, and robust behavior, without overstating automated scan results as conformance.
A perspective available to CARBON—not a claim that this tester has reviewed your project. Findings require execution evidence.
Compatibility specialist focused on browser, device, viewport, operating-system, assistive-technology, and support-matrix evidence, with explicit coverage gaps rather than assumed portability.
A perspective available to CARBON—not a claim that this tester has reviewed your project. Findings require execution evidence.
Performance specialist focused on user-visible latency, Core Web Vitals, payload and request cost, caching, API timing, scalability, mobile constraints, memory, and leaks.
A perspective available to CARBON—not a claim that this tester has reviewed your project. Findings require execution evidence.
Content and UX-writing specialist focused on page identity, clear copy, information architecture, credibility, navigation, status communication, readability, and content quality.
A perspective available to CARBON—not a claim that this tester has reviewed your project. Findings require execution evidence.
Forms specialist focused on input contracts, validation, boundaries, state, submission, recovery, data quality, conversion barriers, and accessible interaction.
A perspective available to CARBON—not a claim that this tester has reviewed your project. Findings require execution evidence.
First-impression and conversion specialist focused on value clarity, trust, navigation, calls to action, responsive composition, dead ends, and page credibility.
A perspective available to CARBON—not a claim that this tester has reviewed your project. Findings require execution evidence.
Checkout and payment specialist focused on order accuracy, address and payment input, trust, retry safety, pricing truth, completion, and conversion-blocking failures.
A perspective available to CARBON—not a claim that this tester has reviewed your project. Findings require execution evidence.
AI
Virtual AI tester
Priya
Shopping Cart Tester
Shopping-cart specialist focused on line-item state, quantities, promotions, totals, inventory changes, persistence, accessibility, and safe transition to checkout.
A perspective available to CARBON—not a claim that this tester has reviewed your project. Findings require execution evidence.
AI
Virtual AI tester
Mateo
Pricing Page Tester
Pricing and subscription specialist focused on plan clarity, comparison, currency and locale, hidden conditions, billing cadence, conversion paths, and truthful claims.
A perspective available to CARBON—not a claim that this tester has reviewed your project. Findings require execution evidence.
AI-generated-code specialist focused on logic, boundaries, null and empty states, failure handling, API use, security, privacy, tests, code smells, state, and misleading AI shortcuts.
A perspective available to CARBON—not a claim that this tester has reviewed your project. Findings require execution evidence.
Project-aware help for choosing a useful testing workflow.
Jason Arbon CEO, testers.ai
/carbon-help
AIJasonAI Code Review
A long command list is not the same thing as help.
If you just changed an API contract, you need a different next step
from someone reviewing a screenshot or trying to understand an old
Selenium suite. The command names are only useful once they connect to
the work in front of you.
/carbon-help looks at the current project, change,
existing tests, and available CARBON state to recommend an appropriate
starting point.
Advice should have a reason
Suppose your repository contains a new import endpoint and a failing
round-trip test. “Run all testing” is possible advice. “Investigate
export/import data integrity before polishing the form” is more useful
advice.
The command can point you toward a focused feature pass, a quality
domain, test generation, a confidence investigation, or another relevant
workflow. A useful recommendation explains its target, why it matters,
and what evidence it should produce.
It should also recognize the limits of the current environment. No
running service, no test credentials, or a source-only artifact changes
what can reasonably happen next.
Use the question you
actually have
/carbon-help I changed the import API and have 15 minutes; what is the highest-value testing to do locally?
The output is guidance, not proof that the recommended checks ran.
Its value is reducing the effort required to choose a sensible
investigation.
You should not have to memorize every CARBON command before getting
useful testing. Start with the project and the decision. Let the command
selection follow.
Install CARBON at testers.ai/carbon for a supported
coding agent such as Claude, Codex, or Cursor.
