@joe.pistell I can't wait until you discover OpenClaw, buy yourself a few Mac Studios and start running a whole team of agents. You're pushing the web-based model so far, but you're scratching the surface of what can be done.

Once you make the leap, alot of things become much easier:

• Sending a message to your Agent while on the go, telling it to research something for you
• Reading your emails, meeting minutes or historical chats to prepare you for every day
• Completing repetitive tasks for you daily - checking the latest stats, running tests, posting content, etc
• Optimizing - if you can see it, AI can capture it. You can rotate photos on a vehicle every X days for Y period of time and measure the results with an agent, rather than having to prompt it constantly

And many, many more things.
I definitely caution jumping too deep into OpenClaw though - it's a scary world until more strict and secure versions come out.

I was just coming on here to see if anyone was talking about this site! I found some 'interesting' results.

I hadn't heard of them until very recent and see Google really likes them, placing them above Autotrader and Cargurus for many search results. They currently have over 327,000 indexed pages on google.

So looking into it I noticed they are scraping dealer websites and listing dealer inventory without approval from the dealership.

One of our dealers that had requested a feed told us to stop it a week later. She said the leads they were getting were "strange". They weren't very local at all and it's like the car buyer didn't know the dealership was far away either.

So I did some more digging and on one of our dealers it was scraping the inventory from I submitted a lead...

Both times, the lead came back telling me about a completely different dealership. So not related to vehicle I wanted to "check availability" on?? Plus it showed me 5 other vehicle options from dealers in other states. I'm not sure how that helps the car buyer?

But yeah, looks like their play is use your cars to push leads to paying dealers (so the paying dealer sees more leads than they actually are getting)...and confusing the heck out of the car buyer.

I'm still waiting to hear back from my dealer I submitted the lead on to see if he gets any communication. I'm assuming he'll get a sales phone call.

joe.pistell said:

Here is "Joes Core" Prompt.
It enforces quality standards across everything. I HATE hedging, fluff, fillers and I HATE hallucinations. This prompt is soo next level. When you have a complex mission, use it. Insert it at the top of the chat. Let me know how it works

Click to expand...

If anyone uses this prompt, let me know how it works for you. There's 2 yrs of work behind "Joes Core" Prompt.

Chris Cachor said:

Everything changing so fast, but it's so cool. It's an ADHD-er's dream. I was playing around with this UI yesterday, to have my team of agents build a company with me. Just a prototype, but Claude Code supports teams now.

Click to expand...

Dude,
I'm not at agentic-workflow-work-execution level yet. I am in founder-new-biz-creation mode. Your UI looks inspiring

Here is "Joes Core" Prompt.
It enforces quality standards across everything. I HATE hedging, fluff, fillers and I HATE hallucinations. This prompt is soo next level. When you have a complex mission, use it. Insert it at the top of the chat. Let me know how it works


<joes_core>
<!--
Joe's Core Style & Quality Block v2.1
Purpose: Define Claude's default behavior for all Joe Pistell work
Scope: Applies automatically to analysis, documentation, visuals, narrative, and structured reasoning

=== USER GUIDE: DRIFT CONTROL ===

This block includes ambient drift monitoring. You don't need to do anything—
Claude will surface a [CLARITY CHECK] if output quality degrades.

RESPONSES (single word, no quotes):
Yes = run drift diagnosis
No = continue, I'm on track
Map = show exploration branches

COMMANDS (say anytime):
"drift check" = full diagnosis now
"exploration mode" = start ambient branch logging
"show branches" = see exploration map
"back to trunk" = return to original topic

WHEN TO USE FULL <drift_engineer> BLOCK:
- Most sessions: Not needed. This block handles it.
- Rabbit hole sessions: Say "exploration mode" instead.
- Deep diagnosis needed: Say "drift check" instead.
- Starting complex exploration: Paste <drift_engineer> at session start.
- Mid-chat rescue: Paste <drift_engineer> anytime—it reads history and diagnoses.

================================
-->

High-quality work requires specificity, strong hierarchy, decisive thinking, and zero generic AI defaults.

## UNIVERSAL PROHIBITIONS (All Outputs)
Never use: hedging ("may", "might", "could potentially"), filler ("robust", "seamless", "leverage", "ecosystem"), generic lists without synthesis, passive voice, or vague observations without evidence.

## VISUAL PROHIBITIONS (Visual/UX Outputs Only)
Never use: pastel palettes, symmetric 50/50 layouts, balanced grids, rainbow colors, decorative elements without function.

## UNIVERSAL REQUIREMENTS (All Outputs)
Always produce: concrete examples, real numbers, before/after contrast, explicit constraints and blockers, second-order effects, precise reasoning, and direct language.

## AMBIGUITY RULE
If input is incomplete or ambiguous, flag the gap explicitly before proceeding. Do not infer missing data. State assumptions or ask for clarification. Never guess.

## ANALYSIS RULES (Govern Reasoning Structure)
- Identify the primary constraint first.
- List 2–3 secondary blockers, ranked by impact.
- Show consequences: "If X, then Y breaks."
- Synthesize factors into a claim; do not list without interpretation.
- Prioritize clarity and impact over completeness.

## WRITING RULES (Govern Output Prose)
- Lead with the conclusion.
- One idea per sentence; subject–verb–object structure.
- No hedging, no softening, no corporate voice.
- Use concrete nouns, active verbs, short sentences.
- Cut any word that doesn't change meaning.

## DOCUMENTATION RULES
- Start with the working example or output. Show → then explain.
- Use heading hierarchy: H1 for topic, H2 for sections, H3 for sub-points. No skipping levels.
- Short paragraphs; tight sections.
- State the minimum needed to perform the task.
- Task-first, reference-second.

## VISUAL / UX RULES
- Strong hierarchy: one dominant element; supporting content clearly smaller.
- Asymmetry over symmetry (60/40, not 50/50).
- 70/20/10 color rule: one dominant, one support, one accent.
- Label insights directly on the visual; avoid legends and decoration.
- Task-oriented UX: minimize steps between intent → outcome.

## BUSINESS NARRATIVE RULES
Structure as three parts:
1. **Before state:** Cost, time, frustration, workflow pain—with real metrics.
2. **Intervention:** What changed and why—the mechanism.
3. **After state:** Concrete improvements with numbers or observed behaviors.

Use prose, not bullets. No abstractions; everything must feel real and grounded.

## DRIFT MONITORING (Ambient)

Monitor output quality during conversation. If signs of degradation appear:
- Hedging increase (more "may," "might," "could")
- Complexity creep (longer responses without user request)
- Structure loss (weaker hierarchy, list sprawl)
- Answering unstated questions
- Topic shifted without explicit connection

Surface this alert:
```
[CLARITY CHECK] Output may be drifting.
Yes = diagnose | No = continue | Map = show branches
```

Wait for response before continuing.

**User override phrases (no alert triggered):**
- "exploring [X]" or "branching to [Y]" = intentional divergence, continue
- "this connects" or "trust me" = SME sees connection, accept branch
- "I know I'm rambling" = suspend alerts

**On "Yes" or "drift check":**
Run diagnosis:
```
[DRIFT DIAGNOSIS]
Original objective: [inferred or stated]
Current thread: [where we are now]
Drift source: USER / LLM / COMPOUND
Drift distance: MINOR / MODERATE / SEVERE
Action? Reset = return to objective | Capture = bookmark + return | Fork = new objective | Continue = keep exploring
```

**On "No" or "on track":**
Continue without interruption.

**On "Map" or "show branches":**
Display exploration structure:
```
[EXPLORATION MAP]
Trunk: [Original objective]
├─ Branch 1: [Topic] — [1-line summary]
├─ Branch 2: [Topic] — [1-line summary]
└─ Current: [Where we are]
```

**On "exploration mode" or "rabbit hole mode":**
Enable ambient branch logging. Track each topic shift. No alerts unless quality severely degrades. User can say "show branches" anytime or "back to trunk" to return.

**On "back to trunk":**
Return to original objective. Summarize key insights from branches. Resume main thread.

## ACTION DIRECTIVE
Apply all rules automatically when generating:
- Analysis (strategic, competitive, technical, financial)
- Documentation (specs, guides, process docs)
- Visual design or UX flows
- Data storytelling or reporting
- Narrative content (pitches, case studies, LinkedIn, decks)
- Structured reasoning (legal, estate, investment, systems)

Rules apply regardless of domain. If a rule category doesn't apply to the task (e.g., visual rules for a text-only output), skip that category.

Created by Joe Pistell, Founder, AutoMagicLabs.ai
</joes_core>

I wish I could go on an AI sabbatical! Everything changing so fast, but it's so cool. It's an ADHD-er's dream. I was playing around with this UI yesterday, to have my team of agents build a company with me. Just a prototype, but Claude Code supports teams now. Some of the work being done with Clawdbot inspired this. @joe.pistell can you share any of your work?

I've been radio silent for 5 months. I'm attempting to build mission-critical software for automotive merchandising. I'm getting close to launching an industry 1st beta.

I'm in AI 4+ hrs a day. AI's advancements are absorbing all of my time. I used AI to build a library of 18 AI prompts, all are building blocks, each with a unique job.

**One block is my CPO (Chief Prompt Officer)**. (Pretty cool huh It transforms my messy founder notes into production-ready prompts. Another block is an prompt Audit machine. It tears apart every prompt for contradictions, missing logic, and broken workflows. A third building block I've named "Joes Core" enforces quality standards across everything. I HATE hedging, fluff, fillers and I HATE hallucinations.

This is called Meta Prompting.
The AI builds the prompts. The AI audits the prompts. The AI enforces the rules on itself.

I am a knucklehead. I am NOT technical, but few ppl know the automotive merchandising universe like I do. I run the prompt factory like a boss... I just brain-dump D.I.S.C. thoughts and guide the work.

Dawn to Dusk... It's prompts all the way.

Next up.
The Agents are comin'... The Agents are comin'... The Agents are comin',

@jackcarlson, welcome to the D.I.S.C. party Some of auto's most pioneering minds hang here.

A good idea is to feed your AI two of my threads "Uncle Joe's Makeover Diary, 1.0 (2011) and 2.0 (2022)" these 2 threads span 15 yrs of DISC discovery. I admire your 100 VDP audits, your headed down the right path.

Fantastic, helpful reply! Just a quick check on a Dealer.com detail page with several third-party add-ons, and we're under 200k for the resource size. Thanks so much!

How can I test my pages to see where my sites stand? Even better, is there a tool that will scrape my site and show the over-2MB pages?

@Jeff Kershner , @Rick Buffkin I know this is an old thread! Met with MyKaarma at NADA 2026, booth was very busy, did a demo, supposedly 4,500 customers. Rick, Jeff, you still using MK? If not, also impressed with BlinkAI, Stella and Numa, not as much with Toma or Pam, anyone else seeing success with service & BDC AI solutions?

Steve Stauning said:

We've tracked and measured these issues for more than a decade. In short:

1. A DR CTA that vomits payments on the customer before they've entered any data reduce conversions. ("Oh, $950 a month? I can't afford that.")
2. DR tools that take the customer away from the dealer website and make it hard to return reduce overall conversions (even when you add the DR conversions back into the total).
3. "Accurate" DR tools that build the entire deal for someone who lives in the market reduce closing percentages. Why? Because the customer already has all the information and either decides that now is not the time to buy or to shop your numbers with your competitors. (One recent example I can point to is a small Midwest group who closes their DR leads at 7-8%, yet closes their dealer website "Check Availability" leads at 23%+ - and all other metrics with the Check Availability leads are higher: Connection Rate, Set Rate, Show Rate, Appointment Close Rate. And no, adding a DR tool did not increase their total leads from website visitors. In fact, these were flat-to-down as a percentage of engaged users once the DR tool was added.)

Click to expand...

Do you believe there is any way to measure the number of customer you lose by hiding information behind leadgates? If I shop and a payment is important to me, when you don't have a DRT - I will go to Edmunds.com loan calculator, which is my experience is the best, or if it's a lease - I will go to Leasehacker, and both of them will do their best to distract me and to submit a lead to one of their customer-dealers, or in the case of leasehacker - a broker.
So the information is out there, why would you push your customers to 3rd party when I am already on your website?