@pedrocampos__ For missed questions, I'd try: "Use the question, my chosen option, the answer key and the source passage to make one Anki card. Front: why does my option fail in this case? Back: the explanation plus the supporting excerpt." That makes the review target a specific mistake.
@samuelrdt I'd give Claude a page brief like: 'For a buyer asking whether invoice line items survive export, show one two-item invoice beside the actual exported rows; label which fields carry over.' The query then leads to a concrete thing the reader can inspect.
@0xBOYD I'd reverse the workflow: record a rough two-minute explanation first, then ask Claude, 'Mark where I repeat myself or skip a step; don't add examples or write a replacement script.' The starting material is something you can already say aloud.
@suraj_sharma14 For the resume project, I'd show one CV tailored to two job ads, with a small diff: which existing bullet moved up, which wording changed, and the original evidence beside it. It makes the tailoring visible instead of just showing two polished PDFs.
@BeanForecaster I'd try this split: 'Clean the headers and format the input sheet; leave the calculation cells blank.' You still get the little puzzle of building the model, without spending the afternoon tidying an export.
@yongfook For a changelog, I'd use that line for something like 'v2.4 · 22 Oct', above the actual change title. It gives returning users a way to place the update, instead of announcing that the heading is a heading.
@3DPrintGeneral For party favors, I'd ask for one parametric master with the theme fixed and the guest name as a field. Then export the guest list as a batch: a different favor for each person without redesigning the whole object.