Skip to content
View claygeo's full-sized avatar

Block or report claygeo

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
claygeo/README.md

Clay George · AI Engineer

I build production LLM systems and find where they bleed money. Started in warehouse ops, taught myself to code to kill the manual work my team was drowning in. Now I ship agent systems, evals, and data pipelines, built to run cheap. Cost discipline isn't a feature I bolt on, it's how I build.

Live at claygeo.dev

Flagship work

competitive-intel-platform — Production data engineering at scale. A 15-state, 1,000+ location competitive pricing pipeline: reverse-engineered 3 proprietary retail APIs under Cloudflare with Playwright, a BullMQ + Redis worker fleet, Postgres normalization across 2,200+ brands, OCR via Google Vision. 175K+ products tracked, 13M+ historical price points. Replaced a 2-week manual cycle with same-day data. Used daily by my pricing team since October 2025.

warehouse-labeling-system — My first production system, still running. Scan-to-print 4x6 thermal labeling for a regulated cannabis facility: Zebra ZT610 integration, three messy inventory export formats normalized with dynamic column detection, offline-first three-tier catalog cache. Prototyped on the warehouse floor as a logistics coordinator in December 2024; seven major versions later it prints 300+ labels a day, every day.

Claude/Codex Plays — Autonomous agent that plays Pokémon end-to-end from RAM state, adversarially gated so it can't fake its own progress. Agent orchestration, eval-harness design, and honest failure logging. Clips and writeup →

How I work: I ship end-to-end, to production, measured. When one project's exploit rate dropped from 67.7% to 13% on a random sample, I published both numbers and treated the gap as a design problem. I write things down honestly.

Stack: TypeScript · Python · Rust · SQL · Anthropic / OpenAI / OpenRouter / Ollama · eval harnesses · agent orchestration · Postgres · Supabase · Redis · Playwright · Next.js · Netlify / Vercel / Hetzner

More at claygeo.dev · LinkedIn · X

Pinned Loading

  1. competitive-intel-platform competitive-intel-platform Public

    Architecture case study of the production competitive-pricing pipeline I built and run: 175K+ products, 2,200+ brands, 13M+ price points across 15 states. Scraper fleet (BullMQ/Redis), reverse-engi…

    2

  2. warehouse-labeling-system warehouse-labeling-system Public

    Showcase: production warehouse inventory & 4x6 thermal labeling system (Zebra ZT610). Prototyped on the floor Dec 2024, in daily production since, now v7.4.1. React 18 + Vite + Supabase. Production…