AI Portfolio · 2026
This page is the receipt. Here's the conversation that built it.
Curated, not sorted. These are the builds I'm proudest of — the ones I'd lead with if I had only one minute. Each has its own deep-dive.
A Pixieset replacement. Client galleries with print sales, favorites, contracts, and a Lightroom-style cull view. Built for the way I actually shoot weddings — and now used by a handful of photographers who didn't want to pay $300/year for an interface they hated.
For working photographers who deserve software that respects their workflow.
Forty-plus slash commands. Thirty-plus skills. Hooks that watch git, calendar, glucose, and the Things inbox. A memory system that survives context resets. The reason every other project on this page exists.
For an ADHD brain that needs the working memory it doesn't have.
Case study coming soonFifteen-year-old C# system on x86 and Visual Studio 2015. Two greenfield Laravel apps for the same firm. AI as pair programmer in an environment where "move fast" is the opposite of a virtue. Names changed; the constraints are real.
For the engineers who inherit the legacy, and the people who depend on it actually working.
Case study coming soonOne CLI that spins up Traefik, Mailpit, and N Laravel Sail containers without making me edit a single docker-compose file. A dashboard. A TUI. The reason running eight side-projects on one Mac is not a config nightmare.
For Future Me, opening the laptop at 9pm to ship one more thing.
Case study coming soonEach card is a real app, shipped for a real person. No screenshots-of-screenshots, no abandoned prototypes.
Three audiences (career services, leadership, ministry), three landing pages, one Ceci. She wrote the words; I built the system. ceciwooten.com / ceciwilson.com.
A learning tool for the photography fundamentals — aperture, shutter, ISO, the exposure triangle. Built because most "photography courses" are four-hour videos and I wanted something that worked more like flashcards.
RSVP, lodging map, registry, dress-code guide — the whole guest-facing site. Built in the weeks before our wedding. Used by ~150 guests. The deadline was non-negotiable.
Laravel + Inertia + Vue with dark/light, RSS, and writing I actually finish. The portfolio of portfolios — and the place this catalog will probably move next.
A prompt-to-image studio with libraries, history, and a clean grid. Built before the public UIs got good. Still my go-to for batch work.
Employee files, onboarding checklists, document signing. For a friend running a 30-person company who'd outgrown spreadsheets and didn't want BambooHR's price tag.
Job tracking, customer notes, route planning. Built for a lawn-care operator whose previous system was a notebook in his truck.
Smaller utilities. Built for me, mostly. A few of them other people use now too.
A thin proxy in front of Claude's API for routing, caching, and audit logging. Useful when I want Claude-powered scripts that don't live inside a Claude session.
A /remarkable slash command that converts the current Claude document to PDF and ships it to my reMarkable. Read prep docs in a meeting without dragging a laptop.
A static HTML playbook on "AI at home" — quick wins, mobile playbook, Home Assistant integration. Written for the friends who keep asking "how do you actually use it?"
A Things 3 CLI for use inside scripts. Add projects, headings, and todos from any process. Closes the loop between code and the task system.
A small daemon that watches for Claude knowledge-cutoff drift in long-running projects. Niche. Useful enough that I wrote it twice.
I'm an IT Manager and software developer at a small environmental engineering firm in upstate South Carolina. The day job is half infrastructure, half custom software, half end-user support — three halves, which is how the math works in a 50-person company.
I started using Claude in earnest in early 2025. Eighteen months later I've built or co-built more than twenty production-ish apps, none of which exist without AI as a daily pair. Most exist because someone I know needed something specific and I had a way to make it.
I don't sell anything. I don't run an agency. This catalog is not a pitch — it's a record. If something here is useful to you, copy it. If you want to talk about how it works, the contact card is to the right.
Email is best. I read everything, reply to most. Builders, photographers, fellow ADHD-coders especially welcome.
cory@coryw.net