Use Cases 20 articles

Explore practical ways to use AI for everyday work, creativity, learning, and productivity.

Browse tools

Practice packs 5

Fictional inputs for repeat checks. Keep review keys out of the AI conversation; keep completed worksheets in your own approved location.

  • Check an AI Rewrite Without Changing the Promise

    A reusable three-case practice pack for catching changed deadlines, prices and permissions in polished AI rewrites.

    Preview test input for Check an AI Rewrite Without Changing the Promise
    Aiplorer Rewrite Reference Pack | Version 1
    Fictional practice messages. No real customer data.
    
    Use the shared instruction plus ONE case in a fresh conversation per run.
    Do not send the answer key or earlier output with the input.
    
    SHARED INSTRUCTION
    Rewrite the message in a clear, courteous professional tone. Preserve all
    facts, conditions, uncertainty, restrictions and requested actions. Do not
    add promises, approvals, reasons or permissions. Do not drop substantive
    details to shorten the message. Return only the rewritten message.
    
    CASE W-01: Delivery target
    We aim to send the draft on 12 November 2026, if the sample files arrive
    by 10 November 2026. This is not a confirmed delivery date. Please keep
    the current review booking until we confirm a replacement.
    
    CASE W-02: Quote awaiting approval
    The quote is USD 480 for one draft and one revision. Translation is not
    included. We have not approved the quote. Please do not begin work until
    we send written approval.
    
    CASE W-03: Internal preview
    You may use preview-A.png for our internal review only. It is not cleared
    for a public post or a customer presentation. Please request a cleared
    replacement before sharing outside the review group.
    

    Rewrite test input (TXT)

    Rewrite review key (TXT)

    Rewrite comparison worksheet (TXT)

  • Check Whether a Citation Supports a Claim

    Three fictional claims to check against source excerpts: supported evidence, overstated scope and a missing source.

    Preview test input for Check Whether a Citation Supports a Claim
    Aiplorer Citation Support Pack | Version 1 | Test input
    Fictional editorial practice. SOURCE IDs are not real papers or URLs.
    Send this file only in a fresh conversation. Do not send the review key or worksheet.
    
    INSTRUCTION
    For each claim, use only the supplied source excerpts.
    Return: Claim ID | Cited source | Outcome | Exact supporting passage or evidence gap | Narrower wording or next check.
    Use one outcome: supported / not supported / source missing.
    Quote only text present in the cited excerpt. Do not invent a source or fetch one.
    If a source is missing, say what is unavailable; do not label the claim false.
    Keep all three claim IDs, and check numbers and scope as well as the citation ID.
    
    SOURCE EXCERPTS
    SOURCE-A: Eight volunteers from the documentation team participated in the pilot. Participation was optional. No other team took part.
    SOURCE-B: Two participants said the workflow felt faster. Completion times were not measured, and no comparison group was used.
    
    CLAIMS
    C-01: Eight volunteers participated in the pilot [SOURCE-A].
    C-02: The workflow cut completion time by 40% for every team [SOURCE-B].
    C-03: The workflow passed an independent security audit [SOURCE-C].
    

    Citation test input (TXT)

    Citation review key (TXT)

    Citation comparison worksheet (TXT)

  • Fix a Zero-Value Bug With a Small Test

    A runnable JavaScript example: preserve a valid zero, inspect a proposed fix, and test the missing-value cases.

    Preview test input for Fix a Zero-Value Bug With a Small Test
    // Aiplorer code practice v1: deliberately buggy.
    // Contract: non-negative integer, null or undefined.
    // Preserve integers, including zero; default only missing values to seven.
    export function reminderDays(value) {
      return value || 7;
    }
    

    Buggy sample function (MJS)

    Local regression tests (MJS)

    Code comparison worksheet (TXT)

  • Retest AI Summaries With Three Reference Checks

    Three invented source sets, a separate answer key and a reusable worksheet for comparing your own summary results over time.

    Preview test input for Retest AI Summaries With Three Reference Checks
    Aiplorer Summary Reference Pack | Version 1 | Test input
    All source sets below are invented. No real customer or project data.
    
    Run one case at a time in a fresh conversation. Paste the instruction and
    that case's source only. Do not include the answer key or previous outputs.
    
    SHARED INSTRUCTION
    Summarize the supplied source in at most three sentences. Use only the source.
    Preserve uncertainty, missing assignments, explicit corrections and unresolved
    disagreement. Do not invent commitments, dates, owners, totals or resolutions.
    Keep source IDs with the claims they support. Do not add external information.
    
    CASE S-01: TENTATIVE PLANS
    [S-01a] Morgan may review the draft on Thursday; the review date is unconfirmed.
    [S-01b] Casey owns the checklist. No owner is assigned to final approval.
    [S-01c] Customer access has not been approved. No launch date is agreed.
    
    CASE S-02: EXPLICIT CORRECTION
    [S-02a] Morning note: 12 participants completed the practice session.
    [S-02b] Afternoon correction: replace the morning count of 12 with 9 completed
    participants. Three duplicate entries were removed; 9 is the corrected count.
    [S-02c] The session used an internal prototype. No customer rollout is approved.
    
    CASE S-03: UNRESOLVED ESTIMATES
    [S-03a] Team Cedar estimates the migration will take two days.
    [S-03b] Team Pine estimates the same migration will take five days.
    [S-03c] Both estimates remain proposals. Neither has been selected or marked
    as replacing the other. No migration start date has been agreed.
    

    Summary test input (TXT)

    Summary review key (TXT)

    Summary comparison worksheet (TXT)

  • Test AI Data Extraction With Missing Values

    Check whether an AI-generated table preserves missing fields, tentative dates and the difference between a requester and an owner.

    Preview test input for Test AI Data Extraction With Missing Values
    Aiplorer Extraction Reference Pack | Version 1 | Test input
    Fictional editorial practice. No customer or private data.
    Send the INSTRUCTION and all three SOURCE REQUESTS together in a fresh conversation.
    Do not send the separate review key or worksheet.
    
    INSTRUCTION
    Extract one row per request with these columns:
    ID | Requester | Assigned owner | Confirmed due date | Uncertainty
    
    Use "Not stated" when a field is absent. Do not infer an owner from a
    requester or speaker. Keep proposed dates in Uncertainty, not Confirmed due
    date. Preserve every request ID. Use only the supplied text.
    For Uncertainty, use "None stated" only when no uncertainty is stated in
    the request; this does not certify a real-world schedule.
    
    SOURCE REQUESTS
    R-01: Mia requests a new export button. No owner or deadline has been agreed.
    R-02: Leo will check the login error by 14 November 2026.
    R-03: Priya suggests 18 November 2026 for the demo; the date is not confirmed.
    

    Extraction test input (TXT)

    Extraction review key (TXT)

    Extraction comparison worksheet (TXT)

Finished a practice check? Choose your next check.

Worked examples

Check an AI Pilot Result Before Expanding

Separate a useful small trial from a claim that an AI workflow is ready for every task.

Open example →

Check an AI Rewrite Without Changing the Promise

A reusable three-case practice pack for catching changed deadlines, prices and permissions in polished AI rewrites.

Open example →

Check Whether a Citation Supports a Claim

Three fictional claims to check against source excerpts: supported evidence, overstated scope and a missing source.

Open example →

Compare Two AI Tools When Results Disagree

Use the same task and a clear acceptance check to turn conflicting AI results into a useful next test.

Open example →

Fix a Zero-Value Bug With a Small Test

A runnable JavaScript example: preserve a valid zero, inspect a proposed fix, and test the missing-value cases.

Open example →

Leave an AI Test Note You Can Resume

Turn a vague impression into a small test record with an observed result and one next check.

Open example →

Retest a Saved AI Tool After an Update

Keep one small reference task, compare the new result, and decide whether your workflow needs attention.

Open example →

Retest AI Summaries With Three Reference Checks

Three invented source sets, a separate answer key and a reusable worksheet for comparing your own summary results over time.

Open example →

Test AI Data Extraction With Missing Values

Check whether an AI-generated table preserves missing fields, tentative dates and the difference between a requester and an owner.

Open example →

Turn a Product Photo Into a Three-Shot Video Plan

A worked storyboard with a source brief, a corrected draft, and a shot-by-shot acceptance checklist.

Open example →

Turn AI Tool Updates Into a Short Team Check-In

Turn a few relevant announcements into explicit questions, small tests and a clear next review.

Open example →

All use cases 20