QPILOT ASK AI — EXPECTED SCREEN TYPE & SAMPLE PROMPTS
=======================================================

For each skill: what kind of screen to point the screenshot at, why that
screen exercises the rules, and a ready-to-use Ask AI prompt. Keep
"Capture screenshot" ON for all of these — none of them require it off.

The Ask AI prompt box allows up to 1500 characters. These prompts are kept
short on purpose, so the AI returns a CONCISE response: verdict + only the
FAILED rules, one line each.

Want the full checklist instead (every rule, pass or fail)? Replace
"List only FAILED rules: [id] severity — evidence. One line each." with:
"List all rules, one line each: [id] PASS/FAIL/N/A — brief evidence. End
with the overall VERDICT."  (N/A = rule cannot be judged from the screenshot.)


-------------------------------------------------------------------------
MOBILE
-------------------------------------------------------------------------

1. wcag_mobile — WCAG Accessibility (Mobile)
   Expected screen: ANY mobile app screen with visible text, icons, and
   tappable controls — a dashboard, a form, or a list view work well.
   Avoid a screen that is mostly a single full-bleed image with no UI.
   Best if it includes: coloured status text (e.g. debit/credit amounts),
   icon-only action buttons, and at least one form field.

   Prompt:
   "Audit this mobile screen against the attached WCAG mobile skill.
   List only FAILED rules: [id] severity — evidence. One line each. No
   passes, no preamble."

2. pci_dss_mobile — PCI-DSS Payment UI (Mobile)
   Expected screen: a CARD-ENTRY or SAVED-CARDS screen — the "Add card" /
   checkout payment form (Card number, Expiry, CVV fields) or a wallet
   screen listing saved cards. A generic dashboard will return mostly
   NOT_APPLICABLE. PAN-masking rules need a SAVED-card view, not a blank
   entry form (a blank form legitimately shows an empty PAN field).

   Prompt:
   "Audit this mobile payment screen against the attached PCI skill
   (PAN/CVV/secure badge). List only FAILED rules: [id] severity —
   evidence. One line each."

3. ecommerce_mobile — E-commerce & Checkout (Mobile)
   Expected screen: the CART or CHECKOUT summary screen showing line
   items, subtotal, discount, tax, shipping and a grand total. This is
   what lets the AI recompute the maths (the skill's core check). A
   product-listing or product-detail page will mostly return
   NOT_APPLICABLE since there's no total to reconcile.

   Prompt:
   "Check this mobile cart against the attached e-commerce skill:
   recompute the total and flag mismatches. List only FAILED rules: [id]
   severity — evidence. One line each."

4. healthcare_mobile — Healthcare & HIPAA UX (Mobile)
   Expected screen: a MEDICATION / PRESCRIPTION view showing dosage
   (value + unit + frequency), or a screen with an ALLERGY banner /
   patient header visible. An empty "no data" state (like a fresh demo
   patient) will return NOT_APPLICABLE across the board — use a patient
   record that actually has an active medication or allergy on file.

   Prompt:
   "Audit this mobile clinical screen against the attached healthcare
   skill (dosage, allergy, PHI). List only FAILED rules: [id] severity —
   evidence. One line each."

5. material_design_mobile — Material Design 3 (Android)
   Expected screen: an ANDROID screen that follows (or is meant to follow)
   Material 3 — ideally a home/dashboard or settings screen where a top
   app bar, a primary button, a FAB and a bottom navigation bar are all
   visible together. The richer the component mix, the more rules fire.
   A full-screen video, game or camera view has no Material components
   to judge and will return mostly NOT_APPLICABLE. Not for iOS screens.

   Prompt:
   "Audit this Android screen against the attached Material 3 mobile
   skill. List only FAILED rules: [id] severity — evidence. One line
   each. No passes."

6. ios_hig — Apple Human Interface Guidelines (iOS, mobile only)
   Expected screen: an iOS screen with a navigation bar and/or a bottom
   tab bar — best is a DETAIL screen pushed from a list (exercises the
   back affordance, safe area and tab bar in one shot), or a screen with
   a modal sheet open (exercises the dismiss-cue rule). The screenshot
   must show the status bar / notch area and the home-indicator area, or
   the safe-area rule returns NOT_APPLICABLE. Not for Android screens.
   There is no web variant of this skill.

   Prompt:
   "Audit this iOS screen against the attached HIG skill. List only
   FAILED rules: [id] severity — evidence. One line each. No passes, no
   preamble."


-------------------------------------------------------------------------
WEB
-------------------------------------------------------------------------

7. wcag_web — WCAG Accessibility (Web)
   Expected screen: ANY web page with body text, inline links, and a
   form — a signup/login page, a content page with links, or a checkout
   form work well. Best if it includes: placeholder-only form fields (to
   test visible-label detection) and at least one inline text link.

   Prompt:
   "Audit this web page against the attached WCAG web skill. List only
   FAILED rules: [id] severity — evidence. One line each. No passes, no
   preamble."

8. pci_dss_web — PCI-DSS Payment UI (Web)
   Expected screen: a CARD-ENTRY / checkout payment screen (Card number,
   Expiration date, Security code fields) WITH the browser's address bar
   visible in the screenshot — the URL is part of what this skill checks
   (PCI-URL-WEB). A saved-cards/wallet screen also works well for the
   PAN-masking rule. Note: on a raw entry form the PAN field is
   legitimately empty/unmasked while typing — that's expected, not a
   failure; PAN-masking really targets a SAVED-card view.

   Prompt:
   "Audit this web payment page against the attached PCI skill
   (PAN/CVV/URL/secure badge). List only FAILED rules: [id] severity —
   evidence. One line each."

9. ecommerce_web — E-commerce & Checkout (Web)
   Expected screen: the CART or CHECKOUT page showing an itemised order
   summary (subtotal, discount, tax, shipping, total) and the checkout
   CTA. Same logic as mobile — this is what lets the AI recompute the
   maths. A product-detail page (like a single product's price/options)
   will return mostly NOT_APPLICABLE since there's no cart total.

   Prompt:
   "Check this web cart against the attached e-commerce skill: recompute
   the total and flag mismatches. List only FAILED rules: [id] severity
   — evidence. One line each."

10. healthcare_web — Healthcare & HIPAA UX (Web)
   Expected screen: a clinical PORTAL view — a patient summary/dashboard
   with Active Medications, Allergies, and the patient header banner
   visible in one screenshot (e.g. an EMR like OpenMRS). Scroll so the
   Allergies widget and patient header are both in frame, otherwise
   HC-ALLERGY-PROMINENCE and HC-PHI-EXPOSURE return NOT_APPLICABLE. A
   print/export screen also exercises the web-only HC-EXPORT-WEB rule.

   Prompt:
   "Audit this web portal against the attached healthcare skill (dosage,
   allergy, PHI). List only FAILED rules: [id] severity — evidence. One
   line each."

11. material_design_web — Material Design 3 (Web)
   Expected screen: a WEB app screen built with Material components — a
   settings, form or dashboard page with one clear primary button, cards,
   and a navigation rail / drawer / top app bar visible. A plain
   marketing page or a site with its own custom design system has no
   Material patterns to judge and will return mostly NOT_APPLICABLE.

   Prompt:
   "Audit this web screen against the attached Material 3 web skill.
   List only FAILED rules: [id] severity — evidence. One line each. No
   passes."


-------------------------------------------------------------------------
QUICK REFERENCE TABLE
-------------------------------------------------------------------------
Skill                   | Best screen                              | Avoid
------------------------|------------------------------------------|----------------------------
wcag_mobile             | Dashboard/form with icons + text         | Blank/image-only screen
pci_dss_mobile          | Add-card form or saved-cards wallet      | Generic dashboard
ecommerce_mobile        | Cart / checkout summary                  | Product listing/detail
healthcare_mobile       | Medication list or allergy banner        | Empty "no data" patient
material_design_mobile  | Android home with app bar, FAB, bottom   | Video/game/camera, iOS UI
                        | nav                                      |
ios_hig                 | iOS detail screen with nav bar + tab bar | Android UI, cropped status
                        | (status bar and home indicator visible)  | bar/home indicator
wcag_web                | Form/content page with links             | Blank/image-only page
pci_dss_web             | Card-entry page WITH address bar         | Cropped page (no URL)
ecommerce_web           | Cart / checkout order summary            | Product detail page
healthcare_web          | Patient summary (meds+allergy+header)    | Empty "no data" patient
material_design_web     | Settings/form page with nav rail/drawer  | Marketing page, custom
                        |                                          | design system

Platform coverage: Mobile = 6 skills, Web = 5 skills. ios_hig is
iOS-only, so it has no web counterpart.

Generated October 2026.
