Case studies
What each project shows
Every project shows one or more parts of product work. Build covers anything I made, from shipped apps to a concept site. Teardown takes apart a product I use and proposes a fix. Documents marks product documents published in full, such as a PRD, test cases or release notes. API marks a published API design. RAG marks retrieval-augmented generation: answers drawn from a set of documents and cited back to them. MCP marks a Model Context Protocol server: tools an AI assistant such as Claude can call directly. Eval marks an evaluation: a system scored against an answer key written before it ran. Each card says exactly what it holds.
Skills by project
| Project | Build | Teardown | Documents | API | RAG | MCP | Eval |
|---|---|---|---|---|---|---|---|
| Prize Stats | |||||||
| Anomaly Upload Validator | |||||||
| Ask the Spec | |||||||
| Ask the Spec in Claude | |||||||
| RefCycle eval | |||||||
| Google Maps: road name corrections | |||||||
| Get to the Point | |||||||
| FleetServ | |||||||
| Gridledger | |||||||
| Off the Shelf | |||||||
| Foreground |
The case studies
Every blank, filled.Prize Stats
A stats API that fills the weekly fantasy football prize results two league platforms could not answer, backtested against weeks I had already settled by hand.
Findings in, findings converted.Anomaly Upload Validator
Checks wind turbine blade inspection findings for required fields and automates the two-step damage taxonomy conversion, taking customer success out of manual validation and engineering off the critical path. The tool is internal; the specification documents are published.
Cited answers, honest limits.Ask the Spec
A retrieval tool that answers questions about the Anomaly Upload Validator's published specification, cites the exact section, and says so when the documents don't have the answer.
Same answers, new door.Ask the Spec in Claude
An MCP server that lets Claude search, read and question the same published specification as Ask the Spec, with the same citations and the same refusals.
Safe before smart.RefCycle eval
One slice of RefCycle built twice from the same brief, once with Claude Code and once with Codex, and scored against an answer key I wrote by hand. RefCycle began as a student concept by a five-person team in the Berkeley UX/UI Boot Camp, UC Berkeley Extension, January 2024. This rebuild and evaluation are solo work.
Google Maps: road name corrections
An independent product proposal: residents with the official record of their road's name have no way to hand it to the map. Built from my own rejected corrections and a county records inquiry.
Say it once, say it clearly.Get to the Point
A spoken-communication coach that scores a delivery on six metrics and highlights exactly where it drifted.
Fleet-wide maintenance.FleetServ
An inspection platform for a fleet-maintenance business specced before the business existed: the truck's condition on the record first, with quoting, scheduling, and invoicing as what a finding turns into.
Every asset, one data layer.Gridledger
A product thesis for an open data layer across renewable energy assets: one asset model, open adapters for any vendor format, and eight stakeholder roles defined end to end.
Every store, one trip.Off the Shelf
A household shopping PWA built for multi-store island runs: aisle-sorted lists, heat-safe trip sequencing, and a purchase memory that answers "have we tried this?" in the aisle.
Surfacing buried tasks.Foreground
A WSJF-based prioritization engine that surfaces the work you keep putting off, and manages its own roadmap as a groomed backlog.
Internal builds I can't show in public are shared by email.