Use Claude Code with previously captured waveform and simulation exports to prepare a difference report with units and conditions through the test workflow below, then review it. Matching tools and permissions are required.
Use Claude Code with a small test project and interface contracts to prepare a work plan, isolated changes and integration log through the test workflow below, then review it. Matching tools and permissions are required.
Text exercise: Provide test companies, public information and product-fit criteria. List dated evidence, matches and unknowns, then draft factual outreach.
Give a text AI paper abstracts, IDs and screening criteria to draft a deduplicated reading-candidate log for human review. This is a drafting exercise; the source used Codex.
Review event times and zones, save the iCalendar draft as .ics, then manually inspect an import in a test calendar.
Provide the brand or event, area and planned visit date. Check organizer and venue notices, distinguishing permanent stores, ended events and unverified information.
Provide a location, date, budget and food preferences. Read the correct branch's official pages and note menu evidence, opening information and check times.
Use an authorized caption copy, preserve provenance and timestamps, check it against playback and manually save a traceable text file.
Supply travel options, time zones, buffers and scoped calendar and message excerpts. Produce a conflict list with supporting text and questions to resolve.
Supply the test site, mockup version, viewport size and page states. Use a page-viewing tool to compare them, then list differences, visual evidence and unobservable areas.
Supply fictional rows and form fields, review the mapped values, then explicitly approve Work test-page prefill for field-by-field checking without submission.
Provide authorized materials, learner level, local curriculum goals and lesson time. Draft activities with purposes, materials, estimated duration and goal sources.
Provide a public page or authorized copy and define the entity types to extract. Produce a list with section locations.
Supply safe household-item photos and local rules to draft material classifications, preparation requirements and questions to verify.
Supply a statement, definitions and assumptions to draft proof steps, counterexample searches and unresolved gaps for expert checking.
Use Cursor with a Godot test scene and acceptance criteria to prepare action logs, screenshots and untested items through the test workflow below, then review it. Matching tools and permissions are required.
Using Codex CLI where available: Supply an existing game copy and level requirements to make a bounded change with test evidence and unfinished work.
Text exercise: Provide de-identified alerts, logs and change records for a defined window. Draft the timeline and next read-only checks.
Supply chores, fixed commitments and available time to draft a flexible plan with priorities, buffers and explicit tradeoffs.
Using Claude where available: Supply one page and confirmed new information to get proposed edits, conflicts and a revised draft.
Use Claude Code with a completed-game PGN and personal notes to prepare review notes separating engine results from explanations through the test workflow below, then review it. Matching tools and permissions are required.
Supply a topic, audience and obtained sources to draft a topic-evidence table, leaving unverifiable search volumes unknown.
Supply synthetic items, units and return rules to design stock movements, balance calculations and known-answer tests before implementation.
Supply a research goal, adult audience and language to draft an unsent questionnaire and flag leading wording or unnecessary personal data.