Stuff I've Built

Started with a landing page, then kept building: enrollment system, cohort portal, blog, assignment tracker. The auth system uses Supabase with an entitlements table. Two cohorts running. The whole site has been rebuilt multiple times in single Claude Code sessions.

The first thing I ever shipped. I had multiple panic attacks making it. Took the workflow I use to finish projects and packaged it. Includes a Claude prompt (the Vibe Coach), a project tracker template, setup guides, and a walkthrough video. Frame your first dollar.

Never finished this one. Scrapes Reddit for posts with confirmed AI/real answers. Players swipe through images and guess. Voting stored in Netlify Blobs. Simple, addictive, and surprisingly hard. Still a great concept.

Made this for my wife Lauren. Built a searchable directory with 3 design themes. Supabase handles the database and auth. Providers can be filtered by specialty, location, insurance. A real professional tool for a real organization. Video of us building it together forthcoming.

Write in Obsidian with "stop markers" (## draft, ## notes). Run the script and only content above the marker goes live. Images auto-copy and convert. One keyboard shortcut from draft to published.

Scrapers pull stats from each platform. Python generates a thermal-receipt-style HTML report with randomized closing lines like "you did the work. now go talk to 847 people."

My wife needed exam prep. Commercial options were terrible. Built an adaptive system that generates questions based on weak areas, tracks performance with charts, and adjusts difficulty. She never really asked for this and I never finished it.

Never finished this but a cool idea no??? First iOS app. Asked Claude to scaffold SwiftUI, wire up Firebase for shared state between two users, and add OpenAI for meal suggestions. Each person can review meals independently.

Never did it but seeing this now I'm like "whoa I should finish this." Wanted a place where good essays surface without algorithmic noise. Built a submit/vote/comment system with client-side search using IndexedDB. No server needed.

In partnership with Good Not Great Industries at the leadership of Mr. Quinn Fenlon. On an Amazon product page, a sidebar slides in showing the same product from other retailers. Rust backend for speed with a Python fallback. Cross-browser compatible.

Gave $100 to an instance of OpenClaw on a VPS and wrote a detailed script in Claude Code for how to handle it. Was deep in the weeds telling the bot to make "V4" and "V2" trades even though I had no clue what any of that meant. Lost $50, maybe more. Definitely the most "this is a drug and the drug is gambling" I've felt with all of this.

Built to onboard Cohort 1 students. Includes a timezone comparison tool (natural language - "what time is it in Tokyo when it's 3pm here?") and a vibe check questionnaire. Helped plan session times across time zones.

The student-facing portal for Code for Creatives. Password-protected, access managed through a Supabase backend. Every week gets updated with session recordings, slide decks, recaps, setup guides, and resources. Built the whole thing from scratch - auth system, page structure, deploy pipeline. Students log in and everything from the course is right there. Managed entirely through Claude Code skills so I never have to touch the code directly to update content.

We were repainting the house and I wanted to preview colors before committing. Built a web app that detects the siding color in a photo using HSL analysis, then recolors it to whatever paint color you pick. Handles shadows, highlights, and different lighting conditions. Upload any house photo and try colors on it. Actually useful, actually used it.

Built for a client. You pick a famous mentor figure, then work through 11 strategic questions to clarify your business positioning and value prop. The AI adapts to the mentor's style and pushes you to get specific. Turns a fuzzy "what do we do" into a sharp answer.

Built a threaded forum for the course community with full Windows 95 styling. User accounts, posts, replies, the whole thing backed by Supabase. Looks incredible. Never actually launched it, but it's sitting there ready to go.

A client ran a national survey (3,000+ respondents) and needed a way to share the results with stakeholders. Built them a password-protected site with data visualizations, demographic breakdowns, and chapter-based navigation. Clean, professional, shareable without sending around a PDF.

Built an interactive companion for a client essay I'm editing. Readers toggle between hierarchical and dynamic team structures across 5 real business scenarios to see where rigid org charts break down. Includes a chatbot so readers can ask questions and connect deeper with the ideas in the essay.

My friend Tommie was thinking about starting a cabinetry business. Built him a full site with warm wood tones, honest pricing pitch ("Beautiful cabinets shouldn't require a second mortgage"), service breakdowns, the whole thing. One conversation, one build session.

A CRM that's just a markdown file. Pipeline tracking, signup status, payment status, outreach history, notes. Connected to Gmail for sending follow-ups, to the access system for granting logins, to Stripe for payment links. No Salesforce, no HubSpot, no monthly fee. Just a file that Claude reads and writes to, and it knows who's where in the funnel at all times.

I describe what the slides are for and Claude generates a self-contained HTML file with all the slides. I open it in the browser and edit text inline - every element is contenteditable. Arrow keys to navigate, escape to stop editing. When I'm done I hit Export, copy the output, paste it back, and Claude incorporates the feedback. The whole thing loops 1-3 rounds until it's right. Five different themes (dark, cream, accent, green, purple), code blocks, two-column layouts, skill tag clouds, flow diagrams. No PowerPoint, no Google Slides, no fighting with templates. Just HTML files I can actually control.

Built for managing social media content across agency clients. Scheduling, drafting, tracking, the whole pipeline. Also scrapes LinkedIn via Apify for posts matching the client's content pillars, refreshes engagement lists, and drafts posts from new content. Internal tool, no public link.

This is my newsletter HQ and it's super important to me. Both Are True is where I write personal essays - funny, dark, honest, weird. The skill has an inbox for ideas, knows the voice (neurotic, absurdist, comedic timing in the white space), and acts as a writing companion for the whole process. Not a generator. A collaborator that understands the tone and helps me get unstuck when I'm staring at a draft.

Three interconnected skills that run a podcast end-to-end. /launch creates a full episode tracker: edit phases, guest coordination, asset checklists, Flightcast upload steps, and launch day sequencing. It also generates interactive HTML launch guides you send to guest teams so they know exactly what to post and when. /social takes clip transcripts and generates platform-specific posts for Instagram, TikTok, and LinkedIn, voice-matched to the host's style, with thumbnail text options. It doesn't summarize clips, it frames them. /titles reads full episode transcripts and generates title options plus two description drafts (one formal, one intimate). The whole system runs a podcast I help produce. Every episode goes through it. Before this existed, launch coordination was scattered across Slack threads and shared docs and stuff got missed constantly.

Scans someone's Claude Code setup locally - their skills, their CLAUDE.md, their folder structure, their commit messages - and generates personalized roasts about the absurdity it finds. Then optionally publishes to a shareable URL so you can send it to people. In active development, should be up soon.

8 clips from one episode, each needing captions for every platform. Doing it manually was 30+ minutes per clip. Built a skill that reads a voice guide and lessons-learned file so the host's voice is consistent. Generates all platforms in one shot. The compounding part: built the voice guide in session 1, added lessons in sessions 2-4, built thumbnails separately. This was the first session where they all worked together. Months of separate pieces clicking into place.

Podcast clips and Reels need thumbnails with bold text overlays. Wanted to try 6 different text options on 10 different frames and pick the best combo in minutes, not hours. Yellow banner, Impact font, auto-sizing text that fills the banner. Extract frames from video at 1fps, curate strong frames, generate thumbnails across all picks. 20 thumbnails in 2 minutes beats 1 perfect thumbnail in 20 minutes.

50+ calls a month across 10 clients. Granola records them all but transcripts pile up. Three different AI sessions might route the same transcript to three different folders. Sub-agent reads the first 15 lines of each, identifies the client, cross-references against what's already filed. Found 25 unfiled transcripts, routed them all. Built an interactive HTML decision tool for 14 remaining cleanup decisions. Click through, copy to clipboard, paste back, everything gets executed.

Ann Wehren asked for the editable HTML slides skill. In under 5 minutes: found the existing skill, cleaned it up for sharing, created a GitHub repo, pushed it. Now anyone installs it with one command: npx skills add alexdobrenko/slides-that-dont-suck. Packaging took longer than building. Your best shareable skills already exist. They're the tools you built for yourself.

Running a 15-person paid cohort. Had two email tools set up. Realized maintaining two platforms for 15 people was pointless. Built a simple Python script that sends individual emails via Resend's API. The CRM is a markdown table. The email preview is an editable HTML file you open in your browser. One API, one markdown file, one Python script. 15 emails sent in 15 minutes. Zero monthly platform fees.

Needed an intake survey that felt personal, not like a Google Form. Claude (Haiku 4.5) plays Alex in a quick intake chat. Asks real follow-up questions based on what people say. When someone types something weird or funny, it rolls with it. On submit, three things fire: submission stored, notification email with CRM-ready row, confirmation email back. Someone testing with "I want to eat more cheese" got a real response instead of breaking.

Asked Claude to clean up my setup. It archived 30 custom skills, treating "old format" as "not needed." Only 2 of them were actually redundant. Built an interactive HTML decision page to sort through the damage. Each archived command got a description, recommendation, restore/skip button, and inline notes. Restored 14, organized related ones into master/subskill structures. AI cleanup is not free. "Simplification" that removes things has a hidden cost you don't notice until you reach for the missing tool.

Needed Britt to review 10 draft posts, 10 engagement targets, and 5 strategy questions. She's on her phone, I'm in the terminal. Built a self-contained HTML decision board with approve/pass buttons, deployed to here.now (3-step API, permanent URL), sent the link via Telegram. Before: "Hey can you look at these 25 things?" via Slack messages that scroll into oblivion. After: one URL, mobile-optimized, tap your decisions, hit Copy, paste back.