The verification drill
Tell, reliably and quickly, when the thing you're learning from is wrong, and build that into a habit rather than a worry.
AI will happily think for you. These methods keep the hard part on your side.
Verify claims. Ask what it does not know. Refuse the full answer. Audit who owned the last session.
Treat this family as standing hygiene for every subject, not an optional advanced track.
Tell, reliably and quickly, when the thing you're learning from is wrong, and build that into a habit rather than a worry.
Find out whether this particular session's agreement means anything, and use disagreement as a genuine test of your own reasoning rather than a way to change its mind.
Instruct it, up front, that it is not allowed to give you answers, only questions.
Make the decision deliberately, so that using it is a choice rather than a default.
Confirm a claim across three independent sources, so one confident paragraph stops being enough.
Mark every paragraph 'I generated' or 'AI generated' and count the ratio, so you can't argue with a number about who did the thinking.
Measure it, by reading your own transcript back.
Find planted errors in AI output: training the verification reflex before you depend on the tool for real work.
Follow every reference to its source before believing it: killing trust in fluent fake footnotes.
Ask the same question several ways and compare the answers, which shows you how much of what you got back was about the subject and how much was about how you asked.
Give it your actual syllabus, notes and marking criteria, so it's answering about your course rather than about the subject in general.
Keep a session to one question rather than drifting, so you leave with an answer, not a tour of the universe.
Use the AI as queryable external memory for a long project while still reconstructing key parts unaided: offload without amnesia.
Require a confidence level on every non-obvious claim, then spend your checking on the low ones.
Treat refining the question as the intellectual work, so each rewrite sharpens what you actually need to know, not just how you boss the model.
Notice where the AI sounds certain without grounds, separating rhetorical confidence from evidential support.
Compare two AI drafts and say which is better and why: training criteria, not passive acceptance of the latest regenerate.
Put the same question to different systems and reconcile: using disagreement as a signal to verify, not as a coin flip.
State format, level, length, and audience precisely, so outputs match the job instead of a generic essay shape.
Give a deliberately incomplete prompt, then diagnose what was missing: training prompt skill by studying failure.
Try to make the AI produce a known wrong answer, then analyse why it did or didn't: mapping failure modes instead of assuming safety.