Sixteen prompts.
Four working examples.

Executed example

Explain DNS to a new office employee. Use writing inspired by ASD-STE100: short sentences, one idea per sentence, active voice where possible, and one term for each concept. Define DNS, resolver and cache. Keep the distinction between finding an address and loading a website. Show a dense before paragraph and a clearer rewrite. Label this STE-inspired, not verified ASD-STE100 compliance. Use Cloudflare's DNS explainer as the factual source: https://www.cloudflare.com/learning/dns/what-is-dns/. Create a readable one-page PDF with the source link and a two-question comprehension check with answers. Render the PDF and inspect it for clipping.

Practice prompt · not executed here

Rewrite the procedure I paste below in STE-inspired English. Use one action per numbered step, consistent terms and explicit conditions. Preserve every warning, measurement and exception. Flag ambiguous instructions instead of guessing. Return the rewrite and a table explaining material changes. Do not claim formal ASD-STE100 compliance. Procedure: [paste your procedure].

Practice prompt · not executed here

Rewrite my recipe for someone cooking it for the first time. Use STE-inspired short sentences and direct actions. Preserve quantities, temperatures, timing and safety instructions exactly. Separate preparation from cooking. Flag missing units or unclear doneness cues. Return a printable one-page checklist. Recipe: [paste your recipe].

Practice prompt · not executed here

Turn the policy below into a plain-language employee guide using STE-inspired writing. Preserve eligibility, deadlines, exceptions and obligations. Keep official terms and define them. Show three examples clearly labelled as illustrations. Highlight anything that needs the policy owner's clarification. Return a before-and-after document. Policy: [paste approved text].

Executed example

Create an editable SVG diagram that teaches a new engineer a simplified retrieval-augmented generation (RAG) workflow. Show two lanes: document preparation (documents -> chunks -> searchable index) and answering (question -> retrieve passages -> enough evidence?). A yes branch gives the question and passages to a model, which drafts an answer with citations; a no branch asks for better evidence. Connect the index to retrieval. Treat the evidence check as our proposed design, not a guarantee built into every RAG system. Use at most ten nodes, labelled arrows and large text. State that citations still need checking. Include an accessible text description. Export the SVG and an HTML page that displays it. Ground retrieval in https://developers.openai.com/api/docs/guides/retrieval.

Practice prompt · not executed here

Explain why Earth has seasons with an annotated diagram for a 12-year-old. Use NASA as the factual source. Show axial tilt, sunlight angle and opposite seasons in the hemispheres. Label scale distortions. Address the distance-from-the-Sun misconception. Produce editable SVG plus a short accessible description, and verify the geometry and labels.

Practice prompt · not executed here

Turn the onboarding process I paste below into a swimlane diagram. Give the employee, manager and IT team separate lanes. Show handoffs, dependencies and waiting points. Mark missing owners as unknown. Return an editable diagram and a table of unresolved decisions. Process: [paste the steps and owners].

Practice prompt · not executed here

Create a labelled diagram explaining a rainwater-harvesting system to a homeowner. Show the roof, gutter, first-flush diversion, storage, overflow and non-potable use. Distinguish a conceptual explanation from an installation design. Verify the mechanism with a public water authority source. Return SVG, a legend and questions to ask a qualified installer.

Executed example

Build a self-contained HTML page that explains a support-review bottleneck. Use synthetic data. Start with 40 incoming tickets/hour, two AI workers at 20 tickets/hour each, one human reviewer, and three minutes of review per ticket. Let me vary arrivals, workers, reviewers and review time. Show agent capacity, review capacity, completed tickets/hour and backlog growth/hour, with the formulas visible. Assume a continuous, steady flow, no starting backlog, no breaks and no rework. Ask me to predict what happens when workers double before revealing the result. Include reset and two example scenarios. Make the page work offline, with keyboard-accessible controls and a mobile layout. Check the baseline, doubled workers and doubled reviewers against hand calculations. Save the complete HTML file.

Practice prompt · not executed here

Build an offline HTML packing planner for a trip. Let me set days, laundry frequency, bag weight limit and item weights. Separate required items from optional items. Show total weight and explain each suggested removal. Use my inputs rather than invented airline rules. Include reset, keyboard controls and a printable list. Check the totals with two hand-worked cases.

Practice prompt · not executed here

Build an interactive HTML lesson on mixing coloured light. Provide red, green and blue sliders, a resulting colour swatch and numeric values. Explain additive light mixing and why this differs from mixing paint. Include three prediction questions with revealable answers. Use an authoritative optics source, accessible controls and a description that does not rely on colour alone.

Practice prompt · not executed here

Create a self-contained HTML café-capacity calculator. Let me vary orders/hour, baristas, preparation minutes/order and espresso-machine capacity. Display the limiting stage and show every formula. Use explicitly synthetic inputs; exclude queue variability and label that limitation. Add two contrasting scenarios and test the arithmetic. Make it usable on a phone.

Executed example

Create a 35-45 second narrated mathematical explainer for team leads: why more AI workers may not speed up approvals. Use this synthetic example: 40 tickets arrive per hour; two workers can draft 20 each; one reviewer takes three minutes per ticket. Animate the flow, show the 20/hour review ceiling, then double workers without changing completed throughput. Finish by doubling reviewers, which raises the idealised completed rate to 40/hour. Label this a simplified steady-flow model with no breaks or rework. Use clear geometric animation and original visual design, English narration, captions, no music, and a readable 16:9 layout. Use an available local speech engine if no voice service is connected. Produce an MP4, an English VTT caption file and representative stills. Check every number and inspect the rendered clip.

Practice prompt · not executed here

Make a 45-second narrated animation explaining why repeated doubling eventually outruns adding ten. Compare sequences starting at one: add ten each step versus multiply by two. Label the axes and compute all displayed values in code. Show the crossing point. Deliver MP4, captions, transcript and stills. Use original visuals and an available speech engine.

Practice prompt · not executed here

Create a 60-second explainer showing how water moves through a plant, for secondary-school learners. Use a university or botanical institution as the factual source. Distinguish roots, xylem, leaves and transpiration. Label simplifications. Deliver a narrated MP4, captions and transcript. Verify that arrows and narration describe the same direction of movement.

Practice prompt · not executed here

Create a 45-second explainer showing why noise-cancelling headphones reduce some sounds better than others. Use manufacturer engineering documentation and an acoustics source. Animate the simplified wave relationship, then show a limitation. Avoid promising perfect silence. Deliver original animation, narration, captions, transcript and three stills. Inspect the final render for sync and legibility.