brianbrady.dev
Available Systems live
FLUENT UI 51 PRS FABRIC UX PARITY AI WORKFLOWS GUARDRAILS ACCESSIBILITY EXPECTED WEB COMPONENTS PLATFORM WRITING NOTES

Frontend systems / Web Components / AI workflows

Interface systems that hold up under product pressure.

Brian Brady works across design systems, frontend architecture, Web Components, and AI-assisted development. He builds tools that reduce drift, remove guesswork, and make good implementation easier.

GitHub Medium Email
Design systems Component platforms Custom elements AI-assisted development Accessibility expectations Product UI infrastructure Parity review Validation workflows

Selected work

Selected work.

01

Fluent UI web components

Built and repaired Web Components inside Microsoft's Fluent UI codebase: custom elements, Storybook examples, high-contrast behavior, keyboard paths, focus states, manifests, and the small edge cases that decide whether a component can survive real product use.

  • web-components
  • a11y
  • storybook
  • focus states
  • dropdowns
Open project
02

Fabric UX web component library

Manage a 120+ component Fabric UX platform built on web components as the source of truth, with thin Angular and React wrappers for enterprise Power BI client migration work across Fabric Web and Fabric Copilot surfaces.

  • web components
  • Angular wrappers
  • React wrappers
  • Power BI clients
Open project
03

Our American Gods

An older automation project with a simple rule: take two public text streams, define a recombination engine, and publish the result on a schedule. Built with Node, Cheerio, request, Twit, timed intervals, and a small text-generation loop.

  • Node.js
  • Cheerio
  • Twitter bot
  • screen scraping
Open project
04

Glyph commerce system

A private commerce application for inventory, symbolic metadata, collection-building, and AI-assisted review. The strange part is controlled; the practical part is product infrastructure.

  • commerce
  • glyph systems
  • interaction design
  • private repo
Open project

How I work

Design intent has to survive production code.

I am a frontend and design systems engineer focused on component architecture, UI infrastructure, and AI-assisted development workflows. Most of my work lives between design intent and production code: tokens, components, wrappers, examples, validation, documentation, and the tools that keep all of it aligned.

Recently, I have been building systems that help AI agents understand product UI the way engineers need them to: with component constraints, accessibility expectations, framework patterns, repository context, and enough guardrails to avoid inventing a second design system in the shadows.

Component reality

Slots, states, wrappers, accessibility APIs, and migration cost matter. Good systems do not pretend otherwise.

Boring correctness

Keyboard paths, visible focus, contrast, state behavior, and examples are product structure, not cleanup work.

AI that earns its keep

Useful automation reduces ambiguity, names tradeoffs, and leaves a better trail than a person could make by hand.

Clean handoffs

Specs, examples, docs, and review notes should make the right implementation feel obvious.

Writing

Notes and essays.

Medium What is worth learning when answers are everywhere? Notes on software, learning, tools, and the weird pressure of increasingly capable machines.

Contact

Available for frontend systems, component platforms, and AI workflow work.

hello@brianbrady.dev GitHub Medium