When you're straining to recall the command, that's the bug
I had seven Claude Code slash commands and couldn't keep them straight. The fix wasn't a cheat-sheet — it was making the agent read my intent.
● Urgent-care operator · AI-agent engineer
A growing share of my urgent-care company's operations runs on a fleet of AI agents I built — and I write down how it actually works so you can use it too.
Intake, scheduling, charting, billing — the whole day, run by agents, with a human on the calls that matter.
How I run it → You build with AIAgent harness, self-verification, recovery, the failures nobody screenshots — written to lift straight into your own agents.
Read the field notes →
I had seven Claude Code slash commands and couldn't keep them straight. The fix wasn't a cheat-sheet — it was making the agent read my intent.
When you point agents at your own knowledge base or project state, resist the urge to let them write directly. The safer pattern is to have the agent derive…
Filing a ticket creates the appearance of progress while nothing is actually owned, scheduled, or moving.
An LLM's attention is cheap and a human's is scarce. Spend the cheap one to protect the scarce one.
A bilingual classical-music learning product that guides people through pieces with stories, context, and things to listen for — not intimidating analysis or assumed expertise.
A single web platform that runs a clinic's whole day — check-in, a live provider queue, lightweight charting, telehealth, staff messaging, and billing — instead of a dozen disconnected legacy tools.
The orchestration layer that launches agent sessions, watches them for trouble — rate limits, context exhaustion, dead sessions — and recovers them automatically, using deterministic scanning instead of fragile notifications.
Building agent systems inside a real business — or running a clinic and wondering what this could look like for you? That's exactly the conversation I want to have. No form, no funnel.