← Back to playbooks
PLAYBOOK · 03 · AI BASICS

AI 101: learn what AI is and how to start using it.

Understand the basic parts of AI, choose a tool for one real problem, and ask for the result you actually want.

Beginner20 minTested · June 3, 2026

Why this works

Most people do not need to memorize every AI product. The tools change too quickly. What matters is understanding the basic pieces: model, app, prompt, context, tools, connectors, agents, and Skills.

AI is software built around large models running on powerful computers. You give it inputs, it gives you an output, and you review the result. This playbook helps you slow down, choose the right starting tool, and ask for the result you actually want.

Run it

  1. Identify the outcome first
    Start with one sentence: I am trying to... Name the result you want at the end. Example: I am trying to turn messy meeting notes into a clear action-item list.
  2. Name the type of work
    Classify the job before choosing a tool. Is this an answer, research, writing, design, organization, automation, coding, or a decision? The category tells you where to start.
  3. Choose a starting tool
    Use Google Search with AI Mode for quick answers and current information. Use Perplexity for source-backed research. Use ChatGPT or Claude for writing and thinking. Use Claude Design for posters, decks, brochures, prototypes, and visual concepts. Use Claude Code or Codex for code and project work. Use Codex for files, meetings, bookkeeping cleanup, email workflows, admin work, and automation.
  4. Load the right context
    Context is the difference between a generic answer and a useful answer. Add the goal, background, audience, constraints, examples, files, meeting notes, emails, calendar details, spreadsheets, links, or Google Drive docs the tool should use. If the tool cannot access something, attach it, paste it, or tell the AI to say what it cannot see.
  5. Ask for the output you want
    Name the format before you run the prompt: answer, source list, draft, deck outline, poster concept, action-item table, automation plan, or code change. If the job is large or unclear, ask for an outline or plan first. If the job is simple, ask for the finished output.
  6. Review and repeat
    Check the output against the result you wanted. If it missed, improve the context, narrow the task, add an example, or switch tools. If it worked, save the prompt so you can reuse it.

The prompt

I am trying to [specific result or task].

Here is the context:
[Attach files, connect Google Drive/email/calendar, paste notes, add links, include examples, or describe the background.]

The output I want:
[Describe the format, audience, level of detail, and anything important to include or avoid.]

If you need more information to do this well, tell me what is missing.

Next 5-minute action