Knowledge Files · The Skipped Step

Markdown Knowledge Files for Dealership AI

The unglamorous step that separates AI that sounds like your store from AI that sounds like everyone's store. Three files. One weekend. Compounds forever.

By the Learn Claude for Dealers team · Updated July 2026 · 6 min read

What a knowledge file is

A markdown file (.md) is just a plain-text document with simple structure — headers, lists, bold. Nothing technical. What makes it powerful is what you put in it: your store's voice, facts, and rules, written so an AI can load them at the start of every task instead of you re-explaining your store in every chat.

If prompts are the instructions for one task, knowledge files are the employee handbook — always in force, no matter the task.

The three files every dealership needs

File 1: voice.md — how your store talks

# [Store Name] Brand Voice

## We sound like
- Confident and direct. Short sentences.
- A knowledgeable friend, not a salesperson.
- Specific: real numbers, real option names, real timelines.

## We never
- Use "act fast", "won't last", "great news!", or ALL CAPS
- Use exclamation marks in customer emails
- Open with "I hope this email finds you well"

## Examples of us at our best
[Paste 3 real emails/descriptions that nailed it]

File 2: store.md — the facts

# [Store Name] Facts

## Basics
- Brands: [X] · Locations: [addresses] · Hours: [hours]
- Key people: [GM, GSM, Service Director — names customers see]

## What we're known for
- [e.g., family-owned since 1987; largest used truck inventory in the county]

## Programs
- [Warranty offering, service perks, loyalty program, trade policy]

File 3: rules.md — the boundaries

# [Store Name] AI Rules

## Hard rules (never break)
- Never quote payments, rates, or lease terms
- Never promise a vehicle is available or will be held
- Never make warranty or condition claims beyond listed facts
- Include [required disclaimer] on advertised prices

## Escalate to a human when
- Customer mentions financing trouble, legal issues, or a complaint
- Anything involving a credit application

How to deploy them

Load all three into a Claude Project. Every conversation in that Project now starts pre-briefed. When a prompt misfires, the fix usually belongs in a file, not the prompt: correct the source of truth once, and every future task inherits it. That's the compounding effect — chats evaporate, files accumulate.

Let AI write the first draft

Here's the trick we teach at the Intensive: don't write these from scratch. Have a 20-minute conversation with Claude — answer its questions about your store, paste in your five best emails — and have it draft voice.md, store.md, and rules.md. Then edit like a manager. AI writing its own instruction files, refined by you, is the modern workflow (it's how spec and PRD files get written on build day, too).