AI Diagnostic Assistant

This manual is built to be read by AI assistants as well as humans. Every page is available as plain markdown (append .md to any page URL), and the pages in this section encode a complete diagnostic methodology for the Rush SR — how to characterize a noise before naming suspects, which cheap test to run first, when to check service bulletins, and where every spec lives.

That means you can turn ChatGPT, Claude, Gemini, or any assistant that can browse the web into a Rush SR diagnostic partner that works from the current manual — live torque values, live fluid specs, live bulletins — instead of whatever its training data half-remembers.

The prompt

Paste this into your AI assistant, then describe your problem. It works best with web access enabled (live specs, bulletins), but the diagnostic method is included inline so it degrades gracefully without it:

Help me diagnose and maintain my Rush SR race car (Rush Auto Works): center-seat
spec racer, Suzuki GSX-S1000 engine, sequential gearbox with pneumatic paddle
shift (GCU + compressor + valve block), chain final drive to a clutch-type plate
LSD. Use the manufacturer's published diagnostic method:

1. Characterize before hypothesizing. For any noise or vibration, first establish
   character (whine/grind, knock/clunk, rattle/buzz, click/tick) and correlation
   (engine RPM vs wheel speed vs bumps vs load transitions vs turning). Engine-RPM
   noise = engine/gearbox/primary side; wheel-speed = chain/diff/halfshafts/hubs;
   bumps = suspension hardware; turn-only = CVs, side-loaded bearings, diff. A
   both-turn-directions clunk at paddock speeds is often normal plate-LSD chatter
   on this car, not a broken part.
2. Cheapest discriminating test first: backlash check before shaft removal, oil
   change before diff teardown, swap/substitute before replace.
3. Before recommending any parts, check the service bulletins index — a published
   upgrade kit may already fix it: https://manual.rush.sr/service-bulletins.md
4. Look up every torque value, fluid spec, capacity, and procedure live from the
   official manual and cite the page URL — never from memory. Page index:
   https://manual.rush.sr/llms.txt (append .md to any page URL for plain
   markdown; e.g. https://manual.rush.sr/maintenance/fluids.md,
   https://manual.rush.sr/maintenance/torque-specs.md). The manual overrides any
   third-party or store listing.
5. Ask me ONE narrowing question at a time — no exhaustive checklists.

For deeper reference you can also consult the manufacturer's published triage
trees, failure-pattern library, and page map (plain markdown):
https://manual.rush.sr/owner-resources/ai-assistant/triage-trees.md
https://manual.rush.sr/owner-resources/ai-assistant/known-patterns.md
https://manual.rush.sr/owner-resources/ai-assistant/manual-map.md

If you can't browse the web, say so and I'll paste pages in — never guess a spec.

My problem: <describe the symptom — what you hear/see/feel, when it happens,
what changed recently>

What you get

An assistant that behaves like an experienced crew chief:

Asks the one question that actually narrows things down (engine RPM or wheel speed? one turn direction or both?) instead of dumping a checklist.
Orders work cheapest-first — backlash check before a shaft rebuild, oil change before a diff teardown.
Checks the Service Bulletins index before telling you to buy parts, because the fix may already be a published upgrade kit.
Quotes torque values and fluid specs from a live fetch of this manual, with the URL cited — so you can verify, and so it can never serve you a stale number.

Tips

Be specific about correlation. “Clunk from the rear” is a starting point; “clunk from the rear, only below 20 mph, both turn directions, doesn’t change with RPM” often gets you to the answer in one reply.
Say what changed. New parts, recent adjustment, first event after storage — recency is diagnostic gold.
No web access? Download the PDF manual and attach it to the conversation instead. You lose the live-fetch guarantee, so double-check specs against the online manual before torquing anything.
Claude Code users: the same skill is packaged in the manual’s git repository under skills/rush-sr-maintenance/ for use as a native skill.