Daclaude

Each capability in Daclaude is a plain-text SKILL.md file — the prompt is the codebase, an Obsidian vault is the persistent state, and ~30 skills handle email triage, voice capture, quests, medical reimbursements, and financial modeling. On a morning walk I can send a voice memo on Telegram; the bridge transcribes it, classifies it against a routing map (ROUTING.md), and files anything above 90% confidence straight into my rolling journal, a project folder, or my task list without me opening a laptop. When a skill falls short, I edit its markdown instructions mid-session: /handoff captures what broke, an adversarial verifier checks the fix, and learnings compound across sessions.

For a while, the system’s biggest problem was that it wrote me too much. By September there were five bot-authored documents in my inbox every week: a content digest, an attention list, a deadline watch, a weekly review, and a weekly journal template. Each made sense when I added it; together they competed for the same few minutes, and some I wasn’t opening at all. The weekly review proposed email filters for me to approve by ticking a box — in five weeks I ticked zero, and its list grew to twelve items nobody read.

Getting it right was mostly deleting. A daily prep note and a weekly recap went in June; a health table, a handwriting-to-journal pipeline, and a reading-review queue followed. What survived are two quiet documents: a Reads Issue on Tuesday and Thursday mornings — newsletters, feeds, and bookmarks synthesized into a single twenty-minute sit-down read — and a Weekly Digest on Fridays centered on one rule in the system’s own instructions: orientation is presence, not productivity. There are no activity logs or streaks to keep; the opening prompt simply asks, “what do i WANT to do this week? and why?”

The issues are also how I talk back to the system. Any inline reply I leave under an item gets processed on a twice-daily pass and receipted in place. If I write "do it" under an item — with an instruction or without one — a background Claude session spins up on its own branch, does the work, and stops at ready-for-review. Anything urgent enough to surface outside that rhythm gets a single line at the top of my notes home page, and deleting the line dismisses it.

Building personal tools with agents turned out to be the fastest way to build intuition for AI products. Every failure mode I hit in Daclaude — OAuth tokens expiring silently, skills that couldn’t coordinate mid-session, append-only memory turning into noise, and the gap between “works in a demo” and “works every morning for six months” — taught me something concrete about agent architecture before I had to make the same call at work.