Creating AI-built tools for everyday people.
If I have an idea, I open Claude Code and start building it. With Claude and OpenAI's Codex I've built a client app that handles health information, tools for my hospital IT job, and custom development tools for the Unity engine. Along the way I built my own setup: agents working side by side, skills I wrote for them, and tests that check what they produce.
I work in desktop support at a hospital, and I built the app below for a fitness studio in Stamford, CT.
01 Method
How I build with AI
Agents write most of the code. I decide what gets built, write the rules they follow, and review the work before it lands. Every project below was built this way.
The pipeline
Project setup
Before any code, I write the instruction files (.md) agents read first: rules, project layout and tests to run.
Code agent
Claude Code asks clarifying questions first, then builds each feature in the real codebase, following those files.
Checks
Runs the tests for every system it touched and looks at screenshots of the result.
My review
I approve it or send it back. Nothing destructive runs without my sign-off.
What makes it work
Several agents at once
Claude Code and OpenAI Codex work in parallel, and neither edits the other's files.
Custom skills
Procedures agents load on demand, such as driving a live game editor.
Memory between sessions
About 60 notes carry decisions and dead ends forward, so agents don't repeat mistakes.
Written rules
Every agent follows the same rules: flag errors instead of hiding them, keep each value in one place, keep passwords out of the code, and never treat a user's text as a command.
02 AI for the people who help clients
Summaries, intake and answers
For The Body Reflex, a Pilates and fitness studio in Stamford where I worked for over a year, I built a client app and a staff dashboard, and redesigned the studio's website. Clients share health information when they join, and the studio's booking system doesn't help staff review it. Go-live is planned for November 27, 2026.
A summary of each new health form
Case summarization and intake
How it works
It saves reading time without replacing the reader.
A trainer gets a short summary and a list of health flags for each new client. The summary is labelled as a draft to check, and the full form is always beside it.
Every flag has to show its source.
Each flag must quote the client's own words. If the quote isn't in the form, the flag is thrown away before anyone sees it.
Measured: 60 of 60.
Across 48 test runs it caught every health flag it should have, and flagged no healthy client. Each summary takes about 7 seconds and costs about 2 cents.
The client app, with an assistant built in
Information retrieval
How it works
The assistant answers routine questions, with the source.
Clients ask about classes, prices and hours. The assistant answers only from the studio's own published content and names the page the answer came from.
It knows when to hand over to a person.
Health questions are declined, with an offer to pass the question to the client's trainer.
A wrong price never reaches a client.
After the AI answers, the server checks every price, phone number and email against the studio's content. If one isn't there, the client is told to call the studio instead.
Website enquiries land where staff already look.
Contact-form messages and newsletter sign-ups from the studio's website show up on one page for every trainer and the owner, with a count in the header and a line in their “Needs your attention” list.
03 Keeping it responsible
Private health information stays private
I work in a hospital, so I treat health information as something a tool has to earn access to. These are the rules built into the studio app.
The rules
The AI never learns who the client is.
It receives health answers with an age in place of the birth date and no name, and nothing at all unless the client has agreed. If a client withdraws that agreement, what the AI wrote about them is deleted.
Every look at a health record is written down.
Health forms are encrypted. Reading one always leaves a record of who read it and when, including attempts that were refused.
Staff see only their own clients.
The database enforces who can see what, so a mistake in the app can't expose someone else's records. 179 automated tests check it, including ones that sign in as the wrong person and confirm they are refused.
Built on made-up data.
Every client and health detail used to build and test it is invented. No real client's information has been near it.
04 Work smarter
Bringing AI into my day job
Smaller tools I built between tickets while our team spent nine months replacing 8,000 devices throughout the hospital. At that scale, every second counts.
Repeat fixes on a hospital help desk
Built for my own tickets. No patient data.
-
Disk Space Cleanup
Low-storage tickets kept coming up, each with the same manual steps. This tool runs them in order, protects logged-in users and shared clinical accounts, and logs the space freed per item for the ticket notes. I use it at work.
Command Prompt
-
Driver Search & Install
It scans a PC's devices, explains each problem in plain English, works through seven fixes while asking before each change, and writes a report for the ticket. Built and tested at home; not yet used on hospital PCs.
Command Prompt
Hospital Wayfinder
Built for my own use. Working prototype.Hospitals are confusing to get around, and ours had no floor map that was easy to pull up. I built a tool that takes the partial floor maps from AeroScout and stitches them into searchable maps with directions. I used it daily in my first weeks while learning the buildings.
What it does
No patient data involved.
Type a room, get a route.
Enter a room number or a PC's name and it gives step-by-step directions across floors, including which elevator to take.
It reads the room numbers itself.
The tool reads the labels off the drawings instead of someone typing them in, about 2,500 so far, and ignores drawing codes and measurements.
It says when it's estimating.
If a room isn't on the map yet, it routes to the nearest numbered room and says so.
Nothing to install.
It runs as a single file on locked-down hospital PCs. Every floor is mapped and labelled. Routes work where corridors have been traced, which is only part of the campus so far.
05 Off the clock
Off-the-clock development
Outside work I make games in the Unity engine, from timed game jam entries to a full Steam release.
How it's built
CLI and MCP connect agents straight to the tools.
Agents drive the open Unity editor through its command line (CLI), about 140 commands, so they place objects, run tests and take screenshots themselves instead of hand-editing files. Over MCP, the standard for plugging tools into AI agents, the code agent pulls designs straight from Claude Design.
Happy to show any of this working.
I can walk you through the app, the tests or the tools on a call or in person.