Five receipts,
one live concept.
Zero to seven brands on one token architecture. A design-to-test workflow a PM can run without a build ticket. A support queue that shrank by a third. A token system carrying twelve themes with zero component edits. A tool that went paid, so a free one shipped. And a concept you can operate in the browser: ground control built for the minute things go wrong.
Each one is written the way a buyer reads it: the outcome first, the mechanism second, the craft last.
- Concept · Operator interfaceSelf-initiatedCS-01 / 06
A drone ground-control interface designed for the minute things go wrong
Tempering is the step that makes steel hold up under stress. TEMPER applies the same idea to an interface: ground control for one autonomous survey aircraft, designed around the minute the link drops and the battery hits reserve, not the twenty minutes when nothing happens. A self-initiated concept, built live, with simulated data.
- To answer: is everything okay, and if not, what?
- 1s
- Alert levels, each with its own shape and label
- 3
- Minimum height for every primary action
- 56px
- Decorative colors in the operator interface
- 0
48-hour sprint · 2026
Read the case study - Design systemMulti-brand publisherCS-02 / 06
Zero to seven brands on one token architecture — five of them in a single two-week sprint
A performance-marketing publisher operating 10+ owned consumer media brands had no shared styling vocabulary. Every brand's Figma kit carried its own hardcoded hexes and its own spacing improvisations, so a styling change was N hand-edits and a QA pass. I built a two-tier token architecture, then built the Figma → Claude → Figma workflow that migrated five brands in one sprint instead of five.
- Brands on a shared token architecture
- 0 → 7+
- Brands migrated in one two-week sprint
- 5
- Token tiers — primitive, then semantic
- 2
- Email UI kits given dark-mode palettes
- 7
4 months, ongoing · 2026
Read the case study - AI workflowMulti-brand publisherCS-03 / 06
Once deployed, a PM can launch a live A/B test straight from an approved Figma design
A performance-marketing publisher's experimentation program was gated on engineering capacity: every test, however small, queued behind a build. I rebuilt an internal Figma-to-Optimizely tool from a Claude skill into a Claude Code plugin, defined the layer-naming convention that separates editable fields from structural ones, and took it through PM and engineering review as a workflow the team runs without me.
- Engineering involvement to ship a test, once deployed
- None
- Path from an approved design to a live test
- Figma → Optimizely
- Roles that can run it, not just me
- PM or designer
- Architecture rebuilt to clear a structural ceiling
- Skill → plugin
3 sprints · 2026
Read the case study - Product redesignF1 ExperiencesCS-04 / 06
Cut support tickets ~40% on a portal serving 22,000+ customers, in two months
The F1 Experiences portal showed customers a billing address and a line item reading Grandstand A75YTZ. That was the entire post-purchase experience for a $5,000 order booked nine months out. Support absorbed the gap, one ticket at a time.
- Fewer “what’s included?” tickets
- ~40%
- Fewer dashboard support inquiries
- ~35%
- Fewer pre-event logistics questions
- ~30%
- Customers on the rebuilt portal
- 22,000+
2 months · 2026
Read the case study - Design systemHeuresCS-05 / 06
A three-collection token architecture, 12 themes, and 21 screens — built solo, with an AI-native workflow
Heures is a calendar PWA designed and built end to end. The calendar is not the interesting part. The interesting part is that every visual property resolves through a token system with zero hardcoded values, it themes across twelve accent sets and four seasonal surfaces without a single component edit, and one person shipped it using the same Claude Code and MCP stack SteelForge installs for clients.
- Token collections — primitives, surface, accent
- 3
- Accent themes × 4 seasonal surfaces
- 12
- Hi-fi screens across 7 flows
- 21
- Hardcoded visual values in the codebase
- 0
Ongoing · 2026
Read the case study - Tooling shippedFigma CommunityCS-06 / 06
A tool I needed went paid, so I shipped a free one
A free-forever Figma plugin that generates full 50–950 Tailwind color scales from any hex and exports them as Figma variables, Tailwind config, CSS custom properties, or JSON. Live on Figma Community, installable in one click.
Open on Figma CommunityShipped, maintained · 2026
Read the case study