P
AI for Automotive Service Technician

Claude Project: Build a Personal Diagnostic Knowledge Base

Time to build: 1.5-2 hours[Common Fault][Fix]Claude

For Automotive Service Technicians

Tools: Claude Pro ($20/mo) | Time to build: 1.5-2 hours | Difficulty: Intermediate-Advanced Prerequisites: Comfortable using Claude for warranty claims and wiring diagrams — see Level 3 guide: "Use Claude's Vision to Analyze Wiring Diagrams"

What This Builds

A Claude Project is a persistent workspace that remembers everything you put into it across every conversation, unlike regular Claude, which forgets everything when you close the tab. Follow this guide and you'll have a personal diagnostic knowledge base loaded with your saved TSBs, known-good repair procedures, common platform failure notes, and your own diagnostic shortcuts. Every conversation in this Project starts with Claude already knowing your entire library.

Instead of re-uploading the same wiring diagrams or re-pasting the same TSBs every session, you build the knowledge once and access it forever. It's like having your own personal AllData — but one that you can ask questions of in plain language.

Prerequisites

  • Claude Pro subscription ($20/month at claude.ai) — Projects require a paid account
  • A collection of TSBs, wiring diagrams, or repair notes you want to save (PDFs work well)
  • A few hours over your first week to load initial content

The Concept

A Claude Project is like a filing cabinet that Claude can search and reference while talking to you. You upload documents, paste in notes, and configure instructions — and every new conversation in that Project has access to all of it automatically. Think of it like this: regular Claude is a colleague you have to brief from scratch every time. Your Claude Project is a colleague who has already read every document in your filing cabinet before you even say hello.

For a service technician, this means: upload the 10 TSBs you reference most often, your shop's common warranty claim language, wiring diagrams for your shop's top vehicles, and notes from complex jobs you've solved — then ask questions about any of it at any time.

Build It Step by Step

Part 1: Create a new Claude Project

  1. Log in to Claude Pro at claude.ai
  2. In the left sidebar, look for "Projects" (it may show as a folder icon or a "Projects" menu item)
  3. Click "New Project"
  4. Name it: "Service Tech Diagnostic Library" (or similar)
  5. You'll see a project workspace with sections for "Instructions," "Documents," and "Conversations"

What you should see: A clean project workspace with three sections and a blank instructions field.

Part 2: Write your project instructions

Click into the "Instructions" section and write your context:

Copy and paste this
This is my personal automotive service technician knowledge base. I work at a franchised dealership.

My experience: [X years], specializing in [brands/systems].
My ASE certifications: [list them].
My shop's primary brands: [list 5-10].

When I ask questions, assume I have these documents available in this project. Reference them when relevant.

My standard request formats:
- "Warranty claim for [vehicle/DTC]" → generate 3 C's narrative from any relevant info in documents
- "TSB for [vehicle/symptom]" → search my uploaded TSBs first, then respond from knowledge
- "Wiring [system] on [vehicle]" → reference uploaded diagrams if available

Always give technician-level responses. Reference specific documents from the project by name when using them.

Part 3: Upload your most-used documents

Click the "Add content" or "+" button in the Documents section. Start with these high-value files:

Recommended uploads (start with these):

  1. Your 5–10 most commonly referenced TSBs (PDF or copy-pasted text)
  2. Wiring diagrams for your shop's top 3 vehicles (screenshots as images, or PDF)
  3. A text file with your "known good specs" — common fuel trim ranges, compression specs, battery CCA minimums for your top platforms
  4. Your shop's warranty claim language guide (if your service manager has one)
  5. Any complex job notes you've written that you want to reference again

How to upload: Click the attachment icon or drag-and-drop files. Claude can read PDFs, images, and text files. For wiring diagram screenshots, upload the image directly. For TSBs, either upload the PDF or copy-paste the text into a text block.

What you should see: Documents listed in the project's knowledge section with file names you can reference.

Part 4: Test the knowledge retrieval

Open a new conversation within your Project (click "New Conversation" inside the project). Try:

  • "What's in my project about [DTC or vehicle platform you uploaded]?"
  • "Find any TSBs I have uploaded for [year/make/model]"
  • "What are my saved specs for [vehicle system]?"

Claude should reference your uploaded documents by name and pull specific information from them.

Troubleshooting: If Claude isn't finding content you uploaded, try asking "What documents do I have in this project?" — this shows you exactly what's indexed and accessible.

Part 5: Build the habit of adding new content

After every complex job you solve, spend 5 minutes adding what you learned to the project:

  • Open a new conversation in your project
  • Type: "Add this to my knowledge base: [vehicle], [complaint], [what you found], [what fixed it], [what to check on a comeback]"
  • Claude will acknowledge it — but more importantly, it's now in the conversation history that the project can reference

Over 3–6 months, you'll have a searchable record of every complex job you've solved.

Real Example: Diagnosing a Recurring Complaint

What you've built: A project with 3 Toyota TSBs, a wiring diagram for the 2021 RAV4 hybrid drive system, and notes from 5 previous HV system jobs.

Scenario: A 2021 RAV4 Hybrid comes in with P0AA6 hybrid battery isolation fault — your third one this month.

Input: "I have another P0AA6 on a 2021 RAV4 Hybrid. Check my notes from previous P0AA6 jobs — what was the root cause on the ones I solved before?"

Output: Claude searches your project's conversation history (where you added notes from previous jobs) and returns: "From your previous P0AA6 jobs: Job 1 (March 3) — root cause was coolant leak from water pump onto HV battery harness connector C317. Job 2 (March 11) — root cause was degraded insulation on HV cable at the battery pack service cover. Both resolved after cleaning/sealing the leak source and re-testing isolation resistance. Recommend starting with coolant leak inspection around the HV battery and checking C317 connector condition."

Time saved: You go straight to the known failure point instead of restarting the diagnostic sequence from scratch.

What to Do When It Breaks

  • Claude doesn't find my uploaded document → Re-upload the document and name it clearly; search for it directly with "What do I have about [topic]?"
  • Project conversations getting too long → Start a new conversation within the project — documents remain accessible, but long conversation threads can slow responses
  • Uploaded PDF not reading correctly → Try copy-pasting the text content directly instead of uploading the PDF; some scanned PDFs (image-based) can't be read as text
  • Running out of project storage → Claude Pro has generous but not unlimited storage; prioritize your highest-value documents and archive old ones

Variations

  • Simpler version: Use Claude's regular "memory" feature (Settings → Memory) to have Claude remember basic facts about you across all conversations — free tier, but less controlled than a Project
  • Extended version: Create multiple Projects for different specializations — one for electrical/ADAS, one for hybrid/EV systems, one for warranty documentation — each with its own targeted knowledge base

What to Do Next

  • This week: Create the project and upload 5 documents — your most-used TSBs and 2–3 wiring diagrams
  • This month: Add notes from every complex job you solve — by end of month you'll have a searchable diagnostic journal
  • Advanced: Create a structured "Known Issues" document in your project: each entry is [Vehicle Platform] | [Common Fault] | [Root Cause] | [Fix] | [Comeback Check]. Update it monthly and it becomes your personal diagnostic database.

Advanced guide for Automotive Service Technician professionals. Claude Pro ($20/month) is required for Projects. Document uploads are stored within your Claude account — review Claude's privacy settings if you have concerns about shop-confidential documents.