I'm a visual person. Always have been.
A few months ago I set up Nate's Executive Assistant + layered Karpathy's
wiki-style brain on top. Without really realizing it, that combo has been
quietly evolving into my own AI OS — every skill, every workflow, every
reference, all interconnected.
Today I saw a post about HTML artifacts in agent workflows. Something
clicked.
Almost anything I run in Claude Code can be turned into a clickable,
locally-hosted HTML page. A pitch deck. A project status overview. A deep
research output with filters. An ingest flow with checkboxes per proposed
wiki edit. A daily focus dashboard. Whatever the skill produces — text in
chat OR a visual surface I can actually interact with.
I started with my Daily Focus skill. It already:
— scans projects, sessions, tasks, _hot.md — ranks by revenue proximity
— reads my calendar for Maker Time blocks
— outputs today's execution list
Now it also writes a local HTML where I check off my floor + 3 build picks,
add notes, see my streaks. I open it in VS Code's Live Preview —
auto-refreshes whenever the file changes.
The clever bit (or hack, depending on how you see it): no real two-way
sync. A "Copy state" button at the bottom puts every change as JSON on
the clipboard. I paste it in Claude, it updates all the relevant markdown
files. Poor man's sync — nothing to maintain, no server, works offline.
I built an ingest dashboard the same way. When Donna processes 25 raw
files in 5 batches, each batch becomes a card with checkboxes per
proposed wiki edit. Three states: approve, revise (with a required note),
or skip. Click through, paste the state back, she applies only what I
approved. Way more scannable than a wall of text in chat.
Plus a Command Center index.html that lists every dashboard with status,
last-updated time, and quick triggers. One landing for everything.
I've been deep in this for hours and might keep going. Curious how others
are using HTML in their workflows — anyone else stumble onto this?
Any patterns you'd steal?
@nateherk