Cut AI token use and teach Claude your rules with markdown, a folder index and rulebooks

Jeff Su shows six durable habits: convert PDFs to markdown, give AI a folder index, save prompt shortcuts, run an intent check before big tasks, use an API key as a spare entrance, and keep one rulebook file per connected tool.

Jeff Su · YouTube · published Nov 10, 2026 · Work & Operations

Cut AI token use and teach Claude your rules with markdown, a folder index and rulebooks — video by Jeff Su▶ Watch on YouTube
Prompt
Read every file in this folder once and create index.md listing each file's location, a one-sentence description, and when to use it. From now on, read index.md first and open only the files a task needs; read the original PDFs in source-pdfs only as a fallback.

Before doing any work on this task, repeat my underlying intent back to me and propose a step-by-step plan for me to review. Wait for my approval.

Visual breakdown

Jeff Su's six tips that should outlast any model: feed AI lightweight markdown and a folder index to waste fewer tokens, use prompt shortcuts, intent checks and API keys to do less manual work, and keep a rulebook per tool so AI learns your preferences.

The problem: AI tips go out of date whenever a new model ships, and AI wastes tokens and time on heavy files and one-shot requests.

The six tips in order

  1. Markdown shortcutConvert PDFs to markdown so AI skips page layout; his 661 KB PDF became 94 KB
  2. Folder mapAI reads every file once and writes index.md: location, one-sentence description, when to use
  3. Prompt shortcutsText expander for prompts you tweak; skills for recurring multi-step tasks
  4. Intent checkAI repeats your intent and proposes a plan before any work on high-stakes tasks
    Dropped: Plans that miss your criteria
  5. Spare keyGive AI an API key so it can do what used to need a developer
  6. Tool rulebooksOne rules file per connected tool, referenced from claude.md or agents.md
  7. Faster, cheaper outputFewer tokens, less manual work, replies that match your style
Input prepSetup / manualAI agentResult

Rules of thumb he gives

  1. Give AI plain text: markdown over PDF or Word, CSV over messy Excel
  2. Text expander for prompts you tweak; skills for repeatable multi-step tasks
  3. Use an intent check before any high-impact task
  4. One rulebook per connected tool

By the numbers

661 KB → 94 KBPDF vs markdown
90%+smaller reference file
45 mincalendar rule example

Try it yourself

Mount a folder in the desktop version of ChatGPT, Claude or Gemini, then ask in plain English.

  1. Put the PDF in a folder and ask AI to extract the relevant parts into a markdown file
  2. Ask AI to read every file once and create index.md with location, description and when to use
  3. Save a rephrase prompt in a text expander for drafts
  4. Before an important task, paste an intent-check prompt and approve the plan
  5. Ask AI to create claude.md (or agents.md) plus a rulebook per tool, such as a Google Calendar rule
  6. Create an API key for tools without a connector and store it in your keychain

Ask your AI to review your connected tools and draft a rulebook for each one.

Tips and gotchas

  • Never paste an API key into a prompt; store it in Mac keychain or Windows credential manager and type it in yourself.
  • Update saved skills when a new model drops, since old instructions can hold newer models back.
  • Approve a small sample (first five of 200 files) before the whole batch.
  • Let one AI check another's work, and use one good example instead of an overengineered prompt.
  • Tag feedback with hashtags like ## slide 2 so AI knows which comment applies to which part.

Distilled from the video’s captions

How to try it

  1. Open Claude.
  2. Copy the prompt and fill in the [placeholders].
  3. Watch Jeff Su's video for the full walkthrough and setup.

Related use cases

Share