Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
AI Fluency Playbook
Getting Started
How to Use
Core Content
Five Pillars
Exercises
Concepts
Learning Profiles
Archetypes
Pathways
Reference
Resources
Glossary
Tools
Further Reading
GW AI Fluency Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
How AI Actually Works
(section)
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== What this means for how you use AI == Understanding that AI predicts rather than knows changes your approach in practical ways: '''Give it more context, not less.''' The model predicts based on what's in front of it. A vague prompt gives it less to work with, so predictions are more generic. A detailed prompt with context, examples, and constraints gives it much better patterns to follow. This is why [[Prompt Engineering Basics|prompt engineering]] matters. '''Verify, don't trust.''' Since the model is generating plausible text rather than retrieving verified facts, you need to check outputs β especially for specific claims, numbers, dates, and citations. The [[The Fact-Check Habit|Fact-Check Habit]] exercise builds this skill. '''It's a collaborator, not an oracle.''' AI is most useful when you bring judgment and it brings speed and breadth. You know your context, your goals, your stakeholders. It can process information, generate options, and stress-test your thinking faster than you can alone. '''Different models have different strengths.''' GPT, Claude, and Gemini are trained differently, on different data, with different priorities. A prompt that works brilliantly in one may flop in another. This is why the playbook is tool-agnostic β we teach capabilities, not product-specific tricks.
Summary:
Please note that all contributions to GW AI Fluency Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
GW AI Fluency Wiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)