Things I built because I needed them

Our team kept hand-formatting AI-drafted content into clean HTML for the website. Slow, error-prone, and a bad use of anyone's afternoon.

A paste-in editor that turns drafts into clean, ready-to-publish HTML in the browser. I built it as a lead magnet for PH360, and the team uses it in real workflows.

AI outputs markdown. Word doesn't speak markdown. Every document required manual reformatting (headers, bold, tables, all of it) before it was usable.

Paste markdown, click format, and copy. The output pastes into Word with correct heading styles, table formatting, and bold intact. The 20-minute reformat loop takes 10 seconds.

My Jira backlog and my Outlook calendar lived in separate worlds. I'd plan my week in my head, then watch it fall apart by Tuesday because nothing was time-blocked.

A Claude-powered workflow that pulls your Jira tasks, reads your Outlook calendar screenshot, and builds an interactive drag-and-drop week view. Export as ICS and import directly into Outlook.

Every library, park district, and museum near me posts events on its own site. Finding something to do meant juggling a dozen tabs.

I scraped the sources into one place and built a filterable page for local events. I shared it around and the feedback has been great. It's live now.

Researching vendors, briefing prep, processing AI outputs. I was constantly copying URLs out of rich content by hand, ten times a week, every week.

Copy anything, a webpage, an email, a document, then paste it here and get every URL extracted and filterable in one shot. Copy all to clipboard and move on.

2,400+ books in the backlog. Two library accounts. A manual process that needed to happen every week. Annoying enough to automate.

A Selenium-driven Python script that navigates the library catalog, places holds across both accounts, and falls back to interlibrary loan automatically. I haven't placed a manual hold since.