Real-time cost alerts in Slack and CLI. Anomalies surface where engineers already work.
›whoami
Staff product designer and AI engineer. Ten years designing AI products, sole design ownership from zero to one.
›ls work
›
Cloud cost intelligence for engineering teams.
Real-time cost alerts in Slack and CLI. Anomalies surface where engineers already work.
Learning complex cloud architecture directly from backend engineers. Designing tools for the immediate technical team.
Accepting raw AWS tags as-is to build adjacent structures with minimal UI interference.
Adapting IBM Carbon for rapid engineering execution.
Research, interaction models, and execution from seed through two funding rounds. Scaling the platform to market.
Infrastructure tags carry no consistent owner or logic.
A learned ML baseline detects cost anomalies in your environment in real time.
The platform sends cost anomalies in Slack, routed to the relevant team by design, reducing dependency on dashboards.
The resource, opened on the anomaly. Causes ranked by cost correlation — the deploy on top. Acknowledge reports back to the channel.
Routine drift logs quietly. A departure from baseline pages the on-call in 33 minutes.
Every resource carries an owning team. The alert lands in that team's channel, not a company-wide feed.
Rate against baseline, start time and projected impact travel with the alert.
Changes from the 24 hours before the spike, ranked by cost correlation. The deploy sits two minutes before the inflection.
My team's changes is the default view. AWS noise sits one tab away.
An acknowledgement here updates the channel. The team sees it is handled.
Competitors monitor cloud cost for finance. The platform maps spend to the engineers who create it.
I design systems, not screens.
Synchronizing software design systems with industrial manufacturing cadences.
Aligning software component architecture with industrial manufacturing cadences.
The system. Tokens — color, type, spacing, radius — and the components they generate. A design change is a change build already has the name for.
Design in the running product. Engineers build against the live screen, not a spec — what they see is what ships.
The resubmit cycle, collapsed. Days of PDF round-trips become one working session on a living design.
An ask sized to a yes. Months of meetings across teams, managers, and directors — distilled to one pilot feature.
The pilot that shipped. One feature, run end to end on the new cadence — the cadence stuck.
A minimalist audio terminal removing cognitive overload through responsive geometry.
An interactive appliance for psychological rest. Sound stripped of choice to match your mind.
The geometry responds to you. There is nothing to operate.
Two years of diffusion research. The first thing it made was a gift for my father.
Direction
Designed, built, and deployed solo. Wan 2.2 on serverless GPUs. Output resolution matches the source frame.
The live app runs the session behind the reel. GPU asleep between runs.
Consolidating the entire curation and captioning pipeline into one offline workspace. Free and open source.
Curation is re-seeing one set until the right cut is obvious. Each arrangement surfaces a different structure.
Structure gathers near-duplicates before you delete. Color and Person come from perceptual hashes and on-device face clusters.
Every dimension, color, duplicate and tag here is Visionary's real output, on 44 images. The native app does this at a hundred thousand — it's on GitHub.
A curated set only matters if it leaves clean. Visionary writes the caption and packages the folder in the format the trainer already reads.
Each caption is built from a type, a length and opt-in extras — no prompt engineering. Taggers and VLMs write to the same .txt.
Export writes .txt sidecars or one metadata.jsonl. Files renumber in grid order, so your arrangement becomes the training order.
Keep it local, zip it, or scp the set straight to the machine that trains. One way, key auth, nothing stored.
Good tools are subtractive. Every one of these shipped before it was cut or rebuilt.
It processes 100,000 photos in under a minute on an 8 GB machine. The heavy analysis runs in the background while you browse.
Designed and built end to end in Claude Code — one design review at a time.
Dark, neutral chrome. Nothing tints how you read a photograph.
Finder selection, Quick Look, delete to the Trash. Every destructive step is reversible.
MIT, one command, no account, no telemetry. The images never leave your machine.
This is not the negative.