Your AI
Operations Guide
Everything PA Transport needs to run Claude Code — from memory and rules to automations, dispatch tools, and team setup. Built for Ajay and Akash.
Prepared by LiteWork AI
Two Ways Claude Remembers
Claude has two memory systems. One you write (rules), one Claude writes on its own (notes). Ajay gets both in the terminal. Akash's Cowork sessions start fresh each time — no auto-memory yet.
CLAUDE.md
Your Training Binder
Think of this as the training binder you hand a new employee on day one. You write down the rules, and Claude follows them every time.
- "Our fleet is based in Tracy, CA"
- "Always check driver availability before booking"
- "Use our rate sheet for pricing quotes"
Auto-Memory
Claude's Notebook
Claude takes its own notes as you work together. The more you correct it, the smarter it gets — like training a new hire over their first few weeks.
- "Ajay handles dispatch, Akash handles customer accounts"
- "Lam Research loads need temp-controlled trailers"
- Things you said "remember this" about
What Are These Files?
Claude uses simple text files to remember things. Here's what each one does — in plain English.
CLAUDE.md Your instruction manual
Like a training binder you hand to a new hire — your rules, your way.
settings.json Your preference dial
Like parental controls on a TV — choose what Claude can and can't do.
SKILL.md A recipe card
Step-by-step instructions for a specific task, like generating a freight quote.
agents/*.md Job descriptions
Each file describes a specialist role — like hiring an expert for one type of job.
hooks Automatic triggers
Like a doorbell camera — something happens, and it automatically reacts.
.mcp.json App connections
Tells Claude which external tools it can use — like apps on your phone.
.claude/rules/ Organized rule files
Like splitting a big binder into labeled tabs — each rule file covers one topic.
@imports File links inside CLAUDE.md
Like a table of contents — point to other files so your main rules stay short.
Your Rules, Claude's Playbook
Write plain-English instructions about your business, and Claude will follow them in every session. No special format needed.
What to Put in It
We are PA Transport, a freight broker based in Tracy, CaliforniaAlways check driver hours-of-service before assigning loadsOur rate sheet is in the file rates-2024.csvNever promise delivery dates without checking dispatch firstYou don't write this. Just tell Claude:
“Create a CLAUDE.md with our company info: we're PA Transport, run by Ajay and Akash, a trucking company in Tracy CA. We run dry vans and flatbeds.”
Three Layers (Most Specific Wins)
Keep It Organized with @imports
As your rules grow, split them into separate files and link them with @import. Your main CLAUDE.md stays short and clean.
# PA Transport Rules
We are PA Transport, based in Tracy CA.
@rules/safety.md
@rules/dispatch.md
@rules/rates.mdClaude Learns As You Work
When Ajay corrects Claude in the terminal, Claude takes notes automatically. The more he uses it, the fewer corrections needed. Note: Cowork doesn't have auto-memory yet — each of Akash's sessions starts fresh.
PA Transport uses dry vans for grocery runs, not reefers
Learned from correctionAkash handles the DHL account, Ajay handles dispatch
Learned from conversationThe Tracy yard closes at 6 PM on weekdays
Learned from "remember this"You don't write this. Just tell Claude:
“Remember that we never use reefer trailers for grocery runs — always dry vans.”
Get Started in 5 Minutes
No complicated setup. No special skills needed. Just five simple steps.
Open your project folder
The folder for the project Claude is helping you with.
Create a file called CLAUDE.md
Just a plain text file in your project folder.
Write 3-5 rules about your business
Plain English. No special format. Tell Claude what matters.
Start Claude Code
Claude reads your rules automatically every time it starts.
When Claude gets something wrong, tell it
It'll remember next time. The more you work together, the fewer corrections.
A Day With Claude
Here's what Ajay's morning looks like with Claude remembering everything about PA Transport.
Opens terminal, Claude has context
Ajay types 'claude' and it already knows: PA Transport, Tracy yard, today's pending loads. No re-explaining.
Check dispatch for today
'Show me today's dispatch' — Claude pulls from dispatch/drivers.json, shows 6 loads pending, 4 drivers available with HOS remaining.
Akash needs a quote
Akash asks in Cowork: 'Quote for Lam Research, Tracy to Portland, temp-controlled.' Claude checks the rate sheet and generates $3,450 with reefer surcharge.
Driver calls in sick
'Reassign Singh's loads to whoever has the most hours left.' Claude checks HOS, suggests Ravi (8 hours remaining), reassigns 3 loads.
Claude catches an overdue invoice
Claude notices a 35-day-old invoice from Valley Freight. Suggests a follow-up email and drafts it — Ajay just reviews and sends.
This basic flow works with just a CLAUDE.md file. Write your company rules, and Claude follows them every session.
Tips & Tricks
Once you've got the basics, these tips help you get even more out of Claude's memory.
/memory command
Type /memory to edit your CLAUDE.md files and manage auto-memory settings.
Edit directly
Memory files are plain text — open them like any document.
Keep it under 200 lines
Short, clear rules beat a novel. Prioritize what matters most.
Personal preferences
Use @import in CLAUDE.md to link personal rule files, or .claude/settings.local.json for private settings.
/compact saves space
Running low on thinking space? /compact summarizes the conversation so far.
Works across projects
Your global rules follow Claude into every project. Write once, use everywhere.
Shortcuts
Quick commands you can type anytime. Think of them as speed-dial buttons for Claude.
/memory Edit your CLAUDE.md rules and manage auto-memory settings.
Like opening the training binder to update it
/compact Summarize the conversation to free up Claude's thinking space.
Like clearing the desk to make room
/context Check how much thinking space Claude has left.
Like checking your phone's storage
/cost See how much this session has used in tokens and cost.
Like checking your phone bill
/model Switch between different Claude models mid-session.
Like switching from a sedan to a truck for heavy loads
/clear Start a fresh conversation (memory still stays).
Like starting a new page in your notebook
/init Let Claude read your project and create a CLAUDE.md for you.
Like having the new hire write their own onboarding notes
Preferences
Control what Claude can do, which model it uses, and whether it saves memories automatically. Like setting parental controls.
Permissions
Three levels: Always Allow, Ask First, or Always Deny. You choose for each action — like setting screen time controls.
Model
Pick which Claude brain to use. Bigger = smarter but slower. Smaller = faster for quick tasks.
Auto-Save Memories
When on, Claude automatically takes notes as you work. Turn off if you want full control.
See the actual settings file
{
"permissions": {
"allow": ["Read", "Glob", "Grep"],
"ask": ["Write", "Edit"],
"deny": ["Bash(rm *)"]
},
"model": "claude-sonnet-4-6"
}You don't write this. Just tell Claude:
“Set up my settings so Claude can read files but can't delete anything.”
Tool Connections
Without tools, Claude can only talk. With tool connections, Claude can actually do things — read your email, check your calendar, search your files.
PA Transport uses Google Workspace for email and calendar. Both brothers are already connected — here's how it was done for each.
Google Workspace
Email, calendar, and docs — all connected.
Learn more
PA Transport runs on Google Workspace. Claude can read emails, draft replies, check schedules, and search docs — all from one connection.
Slack
Read channels, send messages, search history.
Learn more
Claude can monitor channels for questions, post updates, and search through your team's conversation history.
GitHub
Create pull requests, review code, manage issues.
Learn more
Claude can open PRs, leave code review comments, and track project issues automatically.
Databases
Look up records, run reports, check data.
Learn more
Claude can query your database to pull customer records, shipment status, or generate reports.
Google Calendar
Check driver availability, schedule pickups, manage dispatch.
Learn more
Claude can find open time slots, check driver schedules, and coordinate delivery windows.
Web Browser
Open websites, fill out forms, take screenshots.
Learn more
Claude can navigate load boards, check tracking pages, fill in forms, and capture what it sees.
How Ajay & Akash Connected
Ajay's Connection
Claude Code — Terminal
A custom OAuth app was set up in Ajay's terminal. Ajay signed into Google once, and now Claude Code has full access to his email, calendar, and drive — all running locally.
- Custom OAuth app built by Claude Code
- One-time sign-in, then always connected
- Full Google Workspace access
Akash's Connection
Claude Cowork — Web
Akash was connected through Cowork's built-in integrations. Akash clicked "Add Integration," signed into Google, and was done — no terminal needed.
- Built-in Cowork integration
- Click to connect, sign in, done
- Same Google Workspace access
You don't write this. Just tell Claude:
“Connect Claude to our Google Workspace so it can read email and check the calendar.”
Right now, Google connections live in separate configs. Picture a single operations dashboard where both brothers see email, calendar, dispatch, and customer data in one view — each logged into their own accounts, but sharing the same command center.
What Claude Can Build For You
From simple quote generators to full dispatch monitoring — here's what's possible, and how much setup each one takes.
Load Quote Generator
40 min → 5 min per quote
Reads your rate sheet, checks equipment requirements, factors in fuel surcharges, and generates a formatted quote ready to send.
Just tell Claude where your rate sheet is. It reads the file and does the math.
Dispatch Board Monitor
Saves 2 hrs/day
Watches your #dispatch Slack channel, tracks load requests, and suggests driver assignments based on hours-of-service remaining.
Needs a Slack integration and access to your driver availability data. Once connected, it runs on its own.
Invoice Follow-Up
Never miss a 30-day
Checks your aging invoices, identifies overdue accounts, and drafts professional follow-up emails for your review.
Needs access to your invoicing system or spreadsheet. Claude checks it periodically and flags what's overdue.
Customer Onboarding Portal
1 hr → 10 min per customer
Creates intake forms, sets up customer profiles, configures billing preferences, and sends welcome packets automatically.
Now imagine all four of these in one dashboard — new customer comes in, quote goes out, driver gets assigned, invoice gets tracked. A custom command center could run your entire operation from a single screen.
Can Claude Live in Slack?
You're probably thinking: can I just talk to Claude in Slack and have it remember everything, trigger automations, and run the business from there? Here's the honest answer.
What You Get Right Away (No Setup)
Once your Slack admin adds the Claude app from the Slack Marketplace, anyone on the team can start talking to Claude immediately. Think of it like adding a coworker to your Slack workspace.
Find Claude in the Slack App Store
Go to your Slack sidebar, click "Apps", search for "Claude". It's made by Anthropic (the company behind Claude).
Admin Clicks "Add to Slack"
Whoever manages your Slack workspace approves it. One click. Takes 30 seconds.
Connect Your Claude Account
Each person clicks "Connect" and signs in with their Claude account. This links your Slack to your Claude subscription.
Start Talking
Type @Claude in any channel or DM it directly. That's it — you're live.
Three Ways to Talk to Claude in Slack
Direct Message
Private 1-on-1 conversation. Like texting Claude.
@Mention in a Channel
Tag Claude in #dispatch or any channel. Everyone sees the response.
Side Panel
Open Claude in a sidebar while reading a thread. Ask about what you're looking at.
What It Looks Like in Action
The Honest Truth: What Slack Claude Can't Do
Here's the catch. Slack's Claude is like a smart coworker with amnesia — brilliant in the moment, but starts every new conversation completely blank.
Like a full-time employee who reads the training manual every morning, remembers every correction, and has all the tools.
- Reads your CLAUDE.md rules
- Remembers across sessions
- Uses custom tools (email, calendar)
- Runs automations and triggers
Like a brilliant temp worker — shows up, does great work, but starts fresh every new thread with no background on your company.
- No CLAUDE.md — doesn't know your rules
- No memory across threads
- No custom tool connections
- No automations or triggers
Bridging the Gap: Your Options
So can you make Slack the command center for Claude? Yes — but the fancier the setup, the more custom work is involved.
Levels 1 and 2 you can do on your own today. Level 3 is where the real magic happens — but it takes someone who knows the Claude API, webhooks, and Slack bot architecture to wire it all together. That's the kind of project Savi has already built the foundation for with this playbook.
Recipe Cards for Claude
A skill is like a recipe card — step-by-step instructions for a specific task. You type the command, Claude follows the recipe.
---
name: quote
description: Generate freight quotes from the rate sheet
---
1. Read the customer's load requirements
2. Check rates-2024.csv for applicable rates
3. Check driver availability in dispatch/drivers.json
4. Generate a formatted quote
5. Flag if load requires special equipmentYou don't write this. Just tell Claude:
“Create a skill called /quote that generates freight quotes using our rate sheet.”
Creating a skill means putting a SKILL.md file in the right folder with the right format. Once you see the pattern for one, creating more is easy.
The Filing Cabinet
Your CLAUDE.md is like a sticky note on the wall — always visible. Reference docs are like the employee handbook in the filing cabinet — Claude pulls them out only when needed.
CLAUDE.md
Sticky note on the wall
Always visible. Keep it short — your top rules and identity.
Reference Docs
Employee handbook in the cabinet
Detailed guides Claude opens only when the topic comes up.
When Claude Opens Them
Generating a quote? Claude opens the rate sheet guidelines.
Assigning a driver? Claude opens the HOS compliance rules.
Filing a claim? Claude opens the claims process checklist.
You don't write this. Just tell Claude:
“Create a reference doc with our HOS compliance rules so Claude checks them before assigning drivers.”
Auto-Triggers
Hooks are automatic reactions — like a doorbell camera. Something happens, and Claude automatically runs a check.
Before Booking
Claude checks hours-of-service before assigning any load. Catches compliance issues before they happen.
Example: Verify driver HOS before every booking confirmation.
After Assignment
Claude logs every dispatch assignment automatically. Like a post-flight checklist for your dispatch board.
Example: Log driver, load, and route after every assignment.
On Startup
Claude loads today's delivery schedule the moment it starts. Like a morning briefing.
Example: Load today's dispatch board and pending invoices on startup.
See the actual settings file
{
"hooks": {
"PreToolUse": [{
"matcher": "Write",
"hooks": [{ "type": "command", "command": "python3 lint_check.py" }]
}],
"PostToolUse": [{
"matcher": "Bash",
"hooks": [{ "type": "command", "command": "echo 'Done' >> /tmp/claude.log" }]
}],
"SessionStart": [{
"hooks": [{ "type": "command", "command": "python3 load_context.py" }]
}]
}
}You don't write this. Just tell Claude:
“Set up a hook that checks driver hours-of-service before Claude confirms any booking.”
These checks run great in the terminal — but in a custom command center, they'd show up as live status indicators. Green means compliant, yellow means expiring soon, red means stop. Real-time metrics instead of manual checks.
Hire Specialists for Each Job
Custom agents are like hiring an expert for a specific task. A dispatch optimizer, a quote builder, a compliance checker — each one knows exactly what to do.
Dispatch Optimizer
Checks driver hours-of-service, equipment availability, and route efficiency. Suggests the best assignment for every load.
Quote Builder
Reads rate sheets, factors in equipment type and fuel surcharges, and generates formatted quotes ready to send.
Compliance Checker
Verifies driver qualifications, insurance certificates, and FMCSA filing status. Flags anything expiring soon.
See an example agent file
---
name: dispatch-optimizer
description: Assigns best available driver based on HOS and equipment
tools: Read, Grep, Glob
model: claude-sonnet-4-6
---
You are a dispatch optimizer for PA Transport. For each load:
1. Check driver hours-of-service remaining
2. Verify equipment type matches load requirements
3. Check route distance and delivery window
4. Suggest the best available driver
5. Flag any HOS compliance concernsYou don't write this. Just tell Claude:
“Create an agent that optimizes driver assignments based on HOS and equipment.”
Subagent files need a YAML header (name, description, tools) at the top. The description tells Claude when to use this specialist. Once the first one is set up, creating more follows the same pattern.
Apps for Claude
Plugins are like apps on your phone — they give Claude new abilities. Install the ones you need.
Context7
Looks up the latest documentation for any library or tool.
Learn more
When Claude needs to know how a specific library works, Context7 fetches the most current docs — no more outdated answers.
Playwright
Controls a web browser — click, type, take screenshots.
Learn more
Claude can open websites, fill out forms, click buttons, and capture screenshots. Great for testing or automating web tasks.
Pencil
Creates visual designs and UI mockups.
Learn more
Claude can design screens, dashboards, and app layouts visually — not just in code.
Sequential Thinking
Helps Claude break down complex problems step by step.
Learn more
For complicated tasks, this enables Claude to think through each step methodically before acting.
Memory (Mem0)
AI memory infrastructure for apps and agents.
Learn more
An enterprise memory platform ($0–249+/mo) that stores memories across AI tools. Requires developer setup — not a plug-and-play personal tool.
Filesystem
Lets Claude read, write, and organize files on your computer.
Learn more
Claude can create folders, move files, rename things, and keep your workspace organized.
Advanced Memory
When built-in memory isn't enough. These are enterprise-grade options for businesses with complex needs.
Graphiti
Temporal Knowledge Graph
- Remembers how things connect AND when facts changed (temporal)
- Works across multiple AI tools
- You host it yourself — your data stays yours
Mem0
AI Memory Infrastructure
- Enterprise platform ($0–249+/mo) for storing AI memories
- Works with Claude, ChatGPT, and more
- Cloud or self-hosted — your choice
Where Claude Lives
Ajay uses Claude Code (terminal). Akash uses Claude Cowork (web). Here's what each platform can do.
Ajay's Setup
Claude Code — Terminal
Full power. CLAUDE.md, auto-memory, skills, hooks, agents, tool connections — everything. Ajay is learning the terminal and getting the most out of it.
Akash's Setup
Claude Cowork — Web
Shared projects and tool connections. Akash uses Cowork in the browser — no terminal needed. He still benefits from the CLAUDE.md and rules Ajay sets up.
Terminal (Ajay)
Full memory. All features. Where Ajay manages dispatch and driver assignments.
Desktop App
Full memory. Same power as terminal, but with a regular window.
Code Editor (VS Code)
Full memory. Built right into the editor.
Cowork (Akash)
Individual projects and integrations. Where Akash handles customer quotes and accounts — each session starts fresh.
Slack
No persistent memory. Each thread starts fresh for both of them.
Team Setup
Ajay sets up the rules in Claude Code. Akash benefits from them in Cowork. Here's what's shared vs. personal.
Shared (Ajay + Akash)
The PA Transport playbook — both brothers follow the same rules.
CLAUDE.md— Company rules (fleet info, safety, boundaries).mcp.json— Shared tool connections (Gmail, Slack, databases)skills/— Shared recipes (/quote, /dispatch, /report)
Personal (Each Brother)
Ajay's dispatch preferences vs. Akash's quoting preferences.
.claude/settings.local.json— Ajay's model preferences, Akash's permission tweakssettings.local.json— Model choice, permission preferences.claude/— Each person's auto-saved memories
What Shared vs. Personal Looks Like
SHARED: "Never promise delivery dates without checking dispatch first" — prevents costly miscommunication with customers
Both brothers see thisPERSONAL: Ajay's Claude assigns drivers by HOS remaining. Akash's Claude rounds quotes to the nearest $50 for cleaner invoices.
Individual preferenceWhat if they teach Claude different things?
More specific rules always win. CLAUDE.md sets the baseline for the team, but each person's local settings add their own twist. If Ajay tells Claude to sort drivers by HOS and Akash tells Claude to sort by proximity — each gets their own behavior.
Memory Cascade
Shared memory is powerful on its own — but paired with a command center, both brothers could see the same live dashboard: open quotes, active loads, aging invoices, driver status. Same data, same rules, one screen each.
Claude's Thinking Space
Claude has a limited 'thinking space' for each conversation — like a whiteboard. When it fills up, Claude starts forgetting earlier details. Here's how to manage it.
/compact
Summarizes the conversation to free up space. Like erasing the whiteboard and writing a summary.
/context
Shows how much thinking space is left. Like checking how much whiteboard room you have.
Delegate tasks
Send research to specialist agents so they don't use up your main conversation's space.
Common Questions
Quick fixes for the most common issues.